Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enabling the Idp-Init toggle on a SAMLv2 IDP hides the base ACS url in the view window #2146

Closed
1 task
lyleschemmerling opened this issue Mar 7, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@lyleschemmerling
Copy link

lyleschemmerling commented Mar 7, 2023

Description

See the screenshots below. For IDP-init the ACS URL should /acs/{idpId}/{applicationId} but for SP initiated it is just /acs. Flipping the "Enable IdP initiated Login" toggle hides the base /samlv2/acs URL in favor of the idp-init URL in the integration details view. This may cause a problem as the admin may need the /acs URL for configuring the idp to allow sp-initied logins. We should update the view to show both URLs

Affects versions

1.43.0

Steps to reproduce

Steps to reproduce the behavior:

  1. Create a new SAMLv2 IDP
  2. Click on the green view button on the Identity Providers list page. See the callback url.
  3. Edit the idp configuration by toggling "Enable IdP initiated login" and add an issuer.
  4. Click the green view button again. The original ACS URL is gone and is replaced by the idp-init URL

Expected behavior

We should show both URLs when idp-init is enabled

Screenshots

Screenshot 2023-03-07 at 11 17 10 AM

Screenshot 2023-03-07 at 11 18 37 AM

Screenshot 2023-03-07 at 11 19 07 AM

Screenshot 2023-03-07 at 11 20 01 AM

Community guidelines

All issues filed in this repository must abide by the FusionAuth community guidelines.

Doc

  • Update SAMLv2 IdP doc to explain difference in URLs
@robotdan
Copy link
Member

@robotdan robotdan added the enhancement New feature or request label May 12, 2023
@robotdan robotdan added this to Backlog in FusionAuth Issues via automation May 12, 2023
@robotdan robotdan added this to the 1.46.0 milestone May 12, 2023
@robotdan robotdan moved this from Backlog to Code complete in FusionAuth Issues May 12, 2023
@robotdan robotdan moved this from Code complete to Reviewer approved in FusionAuth Issues May 12, 2023
@robotdan robotdan moved this from Reviewer approved to Done in FusionAuth Issues Jun 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
FusionAuth Issues
  
Delivered
Development

No branches or pull requests

2 participants