Details
-
Bug
-
Status: Blocked
-
High
-
Resolution: Unresolved
-
6.21.0
-
None
-
SR4J Sprint 84, SR4J Sprint 85, SR4J Sprint 107, SR4J Sprint 108, SR4J Sprint 109, SR4J Sprint 110, SR4J Sprint 111, SR4J Sprint 112, SR4J Sprint 113, SR4J Sprint 114, SR4J Sprint 115, SR4J Sprint 116, SR4J Sprint 117, SR4J Sprint 118, SR4J Sprint 119, SR4J Sprint 120, SR4J Sprint 121, SR4J Sprint 123 (6.51), SR4J Sprint 124 (6.52), SR4J Sprint 125 (6.54), SR4J Sprint 126 (6.55), SR4J Sprint 127 (6.56), SR4J Sprint 128 (6.57), SR4J Sprint 129 (6.58), SR4J Sprint 130 (7.00), SR4J Sprint 131 (7.01), SR4J Sprint 132 (7.02), SR4J Sprint 133 (7.03), SR4J Sprint 134 (7.4.0), SR4J Sprint 135 (7.5.0), SR4J 136 (7.6.0) HAPIBounty, SR4J 137 (7.7.0), SR4J 138 (7.8.0), SR4J 139 (7.9.0), SR4j Sprint 140 (7.10.0), SR4j Sprint 141 (7.11.0), SR4J Sprint 142 (7.12.0), SR4J 143 (7.13.0), SR4J 144 (8.1.0), SR4J Sprint 145 (8.1.0), SR4J Sprint 146 (8.2.0), SR4J Sprint 147 (8.3.0), SR4J Sprint 148 (8.4.0), SR4J Sprint 149 (8.5.0), SR4J Sprint 150 (8.6.0), SR4J Sprint 151 (8.7.0), SR4J Sprint 152 (8.8.0), SR4J Sprint 153 (8.9.0), SR4J Sprint 154 (8.10.0), SR4J Sprint 155 (8.11.0), SR4J Sprint 156 (8.12.0)
-
15.1
Description
The Switch User scripts in ScriptRunner can fail with various SSO providers. Known providers that have encountered problems include:
- Layer7
- Okta (specifically, their SAML connector)
- JASIG CAS (which also uses SAML)
- TechTime EasySSO
Usually, this is because those providers overwrite the session variable that Switch User sets to determine the logged in user.
It may be that any fix will be specific to the implementation of the SSO provider. At the very least, we need to document this issue so that users can be aware. We do know that the Switch User scripts can work with a variety of SSO providers, so this is likely an implementation detail in your SSO setup.
Notes
- F5 proxy is affected as well.
Attachments
Issue Links
- mentioned in
-
Page Loading...
