The seige of alphabet soup confusion levied against tech people by microshaft never ceases to amaze me. don't know how you can work in this space and not walk away with brain damage. It's almost like the do it on purpose. <_<
It appears just from wading in this garbage for 5 minutes to me that you establish an oauth2 token via ADSF, then use that to connect to EWS. I assume you need to have exchange configured against ADFS already.
- https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/authentication-and-ews-in-exchange
- https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/development/ad-fs-openid-connect-oauth-concepts
- https://aws.amazon.com/blogs/mobile/building-adfs-federation-for-your-web-app-using-amazon-cognito-user-pools/
So it looks to me like a combination of various things that Perl supports via CPAN:
- Oauth2 (a valid token provided by ADFS being ultimately what allows you to access exchange)
- XML
- SAML
- Active Directory/LDAP
Good luck, idk how you put up with this unnecessary and never ending complication of permutations.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
