We require a SAML app property to map old SAML configuration IDs to site IDs #25636
Assignees
Labels
Changelog: Needs Doc
LTS: Excluded
Ticket that has been excluded from at least one LTS
OKR : Customer Success
Owned by Arno
OKR : Customer Support
Owned by Scott
QA : Not Needed
Release : 23.01.6
Included in LTS patch release 23.01.6
Release : 23.09.6
Release Template Builder
Team : Bug Fixers
Type : New Functionality
Comments
swicken-dotcms
added
Type : New Functionality
Triage
OKR : Customer Success
jdotcms
added a commit
that referenced
this issue
Aug 1, 2023
erickgonzalez
added
LTS: Excluded
|
Only for 23.01 LTS |
dsolistorres
added a commit
that referenced
this issue
Aug 10, 2023
dsolistorres
added a commit
that referenced
this issue
Aug 10, 2023
3 tasks
dsolistorres
added a commit
that referenced
this issue
Aug 11, 2023
erickgonzalez
pushed a commit
that referenced
this issue
Aug 16, 2023
erickgonzalez
added a commit
that referenced
this issue
Aug 21, 2023
erickgonzalez
added
Release : 23.01.6
dsolistorres
added a commit
that referenced
this issue
Mar 1, 2024
This was referenced Mar 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parent Issue
No response
User Story
As a user I want to be able to map configuration IDs used in legacy SAML implementations to site IDs so I do not have to update the login URL on the IDP.
Acceptance Criteria
/api/v1/dotsaml/login/{configuration_id}path should either route to/api/v1/dotsaml/login/{site_id}or be a valid route itself.Proposed Objective
Customer Success
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Ticket: https://dotcms.zendesk.com/agent/tickets/112111
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: