active STS callbacks knowing the endpoint invoked (by Office 365)


http://hyperthink.net/blog/a-simple-ish-approach-to-custom-context-in-wcf/

 

Allowing the endpoint URI configured in Office to select a particular “tenant’s” active STS, using parameters placed after the formal endpoint name.

e.g.  metadata exposes http://foo.com/issuer.svc/office365, but

office SP would use http://foo.com/issuer.svc/office365/DEMO.

The trick is to let attribute the STS callback classes with a service behavior that an capture that endpoint URI actually cited by Office SP – so it can then switch to per-tenant configuration parameters.

Advertisements

About home_pw@msn.com

Computer Programmer who often does network administration with focus on security servers. Very strong in Microsoft Azure cloud!
This entry was posted in office365. Bookmark the permalink.