Timeline for Same origin policy restricts login in Sitecore10.2 application
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 4 at 12:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 7 at 12:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 9 at 11:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 10, 2023 at 10:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 13, 2023 at 9:05 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 15, 2023 at 9:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 13, 2023 at 8:29 | answer | added | Thamizh | timeline score: 0 | |
| Feb 10, 2023 at 11:00 | comment | added | Thamizh | After comparing Config files between existing system (9.2) and new system (10.2), came to know meta data has been incorrectly configured. Now the issue got resolved. Thanks for your support @AnnaGevel | |
| Feb 10, 2023 at 8:39 | comment | added | Anna Bastron |
There were changes in the library Sitecore.Owin.Authentication between Sitecore 9 and 10, for example I had to use additional parameters in the constructor of my CustomIdentityProviderProcessor like this: public CustomIdentityProviderProcessor(FederatedAuthenticationConfiguration federatedAuthenticationConfiguration, ICookieManager cookieManager, BaseSettings settings) : base(federatedAuthenticationConfiguration, cookieManager, settings). It is difficult to investigate this issue on StackExchange without seeing your code, please try posting your question in Sitecore Slack.
|
|
| Feb 9, 2023 at 13:44 | comment | added | Thamizh | Do we need to upgrade Sustainsys.Saml2.Owin library also according to Sitecore 10.2.. Because same architecture is working fine in Sitecore 9.2 application | |
| Feb 9, 2023 at 12:57 | comment | added | Thamizh | @AnnaGavel : No Errors in Owin logs. only these two INFO lines: INFO Sustainsys.Saml2.Owin.Saml2AuthenticationMiddleware - Initiating login to <Entity ID> INFO Sustainsys.Saml2.Owin.Saml2AuthenticationMiddleware - Loading metadata for idp <Entity ID> | |
| Feb 9, 2023 at 11:10 | comment | added | Anna Bastron | As far as I know it should not. Do you use Sitecore Federated Authentication and Owin identity provider for Saml2.0 integration? If yes, please try checking the Owin log file too, it may have login-specific errors. | |
| Feb 9, 2023 at 10:52 | comment | added | Thamizh | @AnnaGavel : We found the error "ERROR Cannot find pipeline with name 'getRenderingRules'." in application logs. But this error even happen on page load not only on Login. Is this issue cause the error "An Error Occurred"? | |
| Feb 8, 2023 at 8:57 | comment | added | Anna Bastron |
You highlighted two HTTP headers: Referrer-Policy and Content-Security-Policy. The Referrer-Policy header controls how much referrer information should be included in the Referer header. Content-Security-Policy instructs browsers to load resources and send requests generated from JavaScript only to allowed domains, i.e. prevent cross-site scripting. So none of them should be causing a server-side error in Sitecore. Please check your Sitecore logs, does it have any error details?
|
|
| Feb 6, 2023 at 22:01 | history | asked | Thamizh | CC BY-SA 4.0 |