building on the weeks success ... at being able to get client_credentials to work, generically, I got to actually success reading hte directory port, too!
Reading a AAD directory class from a windows store app ; seeing how to get SSO-launch experie… http://wp.me/p1fcz8-4Xp via @wordpressdotcom
Slowly approaching what I and then Marc W did for NSA 20+ years ago with secure X.500 directory port reading (back in the days when NSA was fighting despots, and not just surveilling all us...while the main web vendors knowingly look the other way...at how its done). And, in general a lot better than the silly ldap comsec model based on SSL ...that filled in (for 20 years).
Anyways, now to the directory indirectly AUTHORIZING access to APIs , including my own. The project shows how to let a service bus listener act as guard (to my upstream WCF service endpoints). And this is how its supposed to be done (where SB is really just a modern form of X.400... wherein the MTA's tie in to the directory lets directory-based policy control when ports open, for whom, given what conditions...)
But the whole proejct is based onACS, and SWTs, and older oauth endpoint standards.
Should I go ahead and be *trying* to debug the bits of my SB + ACS + mobile API script deployment that dont work (yet)...? or could it be that it will never work (given all the changes ongoing in AAD and ACS, this week, that fundamentally uprade the token getting/passing/formatting fabric?