Timeline for Configure XPM Footprints to overwrite claims in Web 8
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 30, 2016 at 8:08 | comment | added | Peter Kjaer | In any version since it was introduced. I only recall the GloballyAcceptedClaims being needed on the server side and the website isn't the server in this case -- the content service is. I don't know, maybe there's something about your setup that's different from mine. | |
| Sep 30, 2016 at 8:07 | comment | added | Philippe Conil | in Web8 or prior? | |
| Sep 30, 2016 at 8:03 | comment | added | Peter Kjaer | That IS odd -- I've never had to do that to get it working. | |
| Sep 30, 2016 at 7:54 | comment | added | Philippe Conil | I know it sounds odd, but I just tested again, if I remove the GloballyAcceptedClaims from the staging site, claims forwarding stops working. Paul A. from R&D actually made the config change for me to fix the issue. | |
| Sep 29, 2016 at 12:11 | comment | added | Peter Kjaer | If you were missing them in the service, that's fine. But I don't believe you need that section on your website. | |
| Sep 29, 2016 at 11:26 | comment | added | Philippe Conil | I had the forwardedclaims on the website but was missing them also in globalacceptedclaims | |
| Sep 29, 2016 at 8:45 | history | answered | Peter Kjaer | CC BY-SA 3.0 |