Timeline for Not able to impersonate user on custom page, where tridion is enabled with adfs saml authentication
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 30, 2022 at 9:37 | comment | added | Quirijn | I think in this scenario there is no connection between the current user (i.e. a Windows user accessing your custom page) and the AD user which has access to Tridion. I don't see how HttpContext.Current.User.Identity.Name would get you anywhere. To impersonate the user you probably need to look for a claim in the request somewhere - IF that is being set in the first place. | |
| Mar 29, 2022 at 15:05 | comment | added | Rick Pannekoek | Well, "it's complicated" :-) Core Service does support SAML to some extent (it has so-called Federation bindings which let you pass an entire Claim Set in the form of a SAML token). But if impersonating by user name is sufficient, you can do that (using the user named obtained like above). | |
| Mar 29, 2022 at 5:54 | comment | added | Neetesh Narvaria | after getting current user I am getting access denied while trying to create core-service session, is it because SAML configuration? looked into this article as per this I believe core-service does not support SAML tridion.stackexchange.com/questions/21218/… | |
| Mar 29, 2022 at 5:54 | comment | added | Neetesh Narvaria | Thanks @RickPannekoek, was able to get current user from given article. :) | |
| Mar 24, 2022 at 12:58 | comment | added | Rick Pannekoek | Possible duplicate of tridion.stackexchange.com/questions/19566/… | |
| Mar 24, 2022 at 12:21 | history | asked | Neetesh Narvaria | CC BY-SA 4.0 |