-
-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #562 from ITfoxtec/test
Test
- Loading branch information
Showing
172 changed files
with
3,969 additions
and
485 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 3 additions & 1 deletion
4
docs/up-party-howto-oidc-foxids.md → docs/howto-oidc-foxids.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| # Interconnect two FoxIDs tracks with a track link | ||
|
|
||
| FoxIDs tracks in the same tenant can be connected with track links. A track link acts mostly like OpenID Connect but it is simpler to configure and the steps it goes through is faster. | ||
| Therefor a login sequence that jumps between tracks will execute faster using a track link competed with using OpenID Connect. But an [OpenID connect connection](howto-oidc-foxids.md) is required if you need to jump between tracks located in different tenants. | ||
|
|
||
| Track links support login, RP-initiated logout and front-channel logout. Furthermore, it is possible to configure [claim and claim transforms](claim.md), logout session and home realm discovery (HRD) like all other connecting up-parties and down-parties. | ||
|
|
||
| ## Configure integration | ||
|
|
||
| The following describes how to connect two tracks called `track_x` and `track_y` where `track_y` become an up-party on `track_x`. | ||
|
|
||
| **1 - Start in the `track_x` track by creating a track link in [FoxIDs Control Client](control.md#foxids-control-client)** | ||
|
|
||
| 1. Select the Parties tab and then the Up-parties | ||
| 2. Click Create up-party and then Track link | ||
| 3. Add the name e.g., `track_y-connection` | ||
| 4. Add the `track_y` track name | ||
| 5. Add the down-party name in the `track_y` track e.g., `track_x-connection` | ||
| 6. Click Create | ||
|
|
||
|  | ||
|
|
||
| **2 - Then go to the `track_y` track and create a track link in [FoxIDs Control Client](control.md#foxids-control-client)** | ||
|
|
||
| 1. Select the Parties tab and then the Down-parties | ||
| 2. Click Create down-party and then Track link | ||
| 3. Add the name e.g., `track_x-connection` | ||
| 4. Add the `track_x` track name | ||
| 5. Add the up-party name in the `track_x` track e.g., `track_y-connection` | ||
| 6. Select which up-parties in the `track_y` track the user is allowed to use for authentication | ||
| 6. Click Create | ||
|
|
||
|  | ||
|
|
||
| That's it, you are done. | ||
|
|
||
| > Your new up-party `track_y-connection` can now be selected as an allowed up-party in the down-parties in you `track_x` track. | ||
| > The down-parties in you `track_x` track can read the claims from your `track_y-connection` up-party. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
45 changes: 45 additions & 0 deletions
45
src/FoxIDs.Control/Controllers/Master/MRiskPasswordFirstController.cs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,45 @@ | ||
| using FoxIDs.Infrastructure; | ||
| using FoxIDs.Models; | ||
| using Api = FoxIDs.Models.Api; | ||
| using FoxIDs.Repository; | ||
| using Microsoft.AspNetCore.Http; | ||
| using Microsoft.AspNetCore.Mvc; | ||
| using System.Collections.Generic; | ||
| using System.Threading.Tasks; | ||
| using AutoMapper; | ||
|
|
||
| namespace FoxIDs.Controllers | ||
| { | ||
| public class MRiskPasswordFirstController : MasterApiController | ||
| { | ||
| private readonly TelemetryScopedLogger logger; | ||
| private readonly IMapper mapper; | ||
| private readonly IMasterRepository masterRepository; | ||
|
|
||
| public MRiskPasswordFirstController(TelemetryScopedLogger logger, IMapper mapper, IMasterRepository masterRepository) : base(logger) | ||
| { | ||
| this.logger = logger; | ||
| this.mapper = mapper; | ||
| this.masterRepository = masterRepository; | ||
| } | ||
|
|
||
| /// <summary> | ||
| /// Get the first 1000 risk password. Can be used query risk passwords before deleting them. | ||
| /// </summary> | ||
| /// <returns>Risk passwords.</returns> | ||
| [ProducesResponseType(typeof(HashSet<Api.RiskPassword>), StatusCodes.Status200OK)] | ||
| [ProducesResponseType(StatusCodes.Status404NotFound)] | ||
| public async Task<ActionResult<HashSet<Api.RiskPassword>>> GetRiskPasswordFirst() | ||
| { | ||
| var mRiskPasswords = await masterRepository.GetListAsync<RiskPassword>(maxItemCount: 1000); | ||
| if (mRiskPasswords?.Count > 0) | ||
| { | ||
| return Ok(mapper.Map<HashSet<Api.RiskPassword>>(mRiskPasswords)); | ||
| } | ||
| else | ||
| { | ||
| return Ok(); | ||
| } | ||
| } | ||
| } | ||
| } |
Oops, something went wrong.