-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
23
-
Problem
SSO requests are currently exempted from websudo. Users logged in through SSO can go straight into administration functions without a websudo check which poses a security risk.
Solution
Allow websudo to work with SAML/SSO setup as well as to allow websudo to work with other marketplace SAML/SSO plugins.
Workaround
- Set a new password for the user that was created with JIT provisioning: JIT provisioning creates a user in Bitbucket's Internal Directory and you can define a password for this user. As a side-effect, an administrator will have 2 passwords - the IdP password to log in Confluence and the Internal password to authenticate in secure-sessions.
- is related to
-
CONFSERVER-60263 Ability to have the Websudo functionality working with SAML / SSO
- Gathering Interest
-
JRASERVER-69311 Ability to have the Websudo functionality working with SAML / SSO
- Gathering Interest
- depends on
-
AAUTH-20 You do not have permission to view this issue
[BSERV-19537] Ability to have the Websudo functionality working with SAML / SSO
UIS | Original: 8 | New: 23 |
UIS | Original: 9 | New: 8 |
UIS | Original: 16 | New: 9 |
UIS | Original: 14 | New: 16 |
UIS | Original: 10 | New: 14 |
UIS | Original: 4 | New: 10 |
UIS | Original: 3 | New: 4 |
UIS | Original: 4 | New: 3 |
UIS | Original: 3 | New: 4 |
UIS | Original: 31 | New: 3 |