• 4
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      Currently, whenever we set up SAML SSO with any identity provider, the SP-initiated SAML requests are unassigned, so in case we might have a certain level of additional security policies, our identity provider won't allow the user to log in from this unassigned SAML request, even after inserting their credentials in the IDP's login screen.

      Suggestion

      • Insert the ability of adding the signature information in the XML SAML request when users are logging in by IDP-initiated logins.

            [ACCESS-1231] Support signed SAML requests

            Leonardo H added a comment -

            Hi all,

            Thanks to everyone for watching and commenting on this ticket. As part of an initiative to better consolidate customer feedback, we are closing this ticket as a duplicate of ACCESS-1213, which covers this need and has received more traction.

            You can follow the ticket there as the source of truth.

            Thank you again for your feedback!

            Leonardo H
            Atlassian Support

            Leonardo H added a comment - Hi all, Thanks to everyone for watching and commenting on this ticket. As part of an initiative to better consolidate customer feedback, we are closing this ticket as a duplicate of ACCESS-1213 , which covers this need and has received more traction. You can follow the ticket there as the source of truth. Thank you again for your feedback! Leonardo H Atlassian Support

              Unassigned Unassigned
              vsiqueira Vinicius (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: