Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Qu'est-ce que ADFS (Active Directory Federation Services) ?

ayi

So I’ve been told that our PHP application may need to support authentication using ADFS.

<ul>
<li></li>
</ul>
For a non-Microsoft person, what is ADFS?
<ul>
<li></li>
</ul>
How does it differ to things like LDAP?
<ul>
<li></li>
</ul>
How does it work? What kind of information would be included in a typical request to an ADFS server? Is it designed for both authentication and authorization?
<ul>
<li></li>
</ul>
Are ADFS servers typically accessible from the internet (whereas corporate AD domain controllers would not be)?

I’ve tried reading some of the Technet docs, but it’s full of Microsoft-speak that isn’t hugely helpful.
Wikipedia is better (see below), but perhaps some of the ServerFault community can fill in some of the gaps.
<blockquote></blockquote>
Active Directory Federation Services (ADFS) is a software component developed by Microsoft that can be installed on Windows Server operating systems to provide users with single sign-on access to systems and applications located across organizational boundaries. It uses a claims-based access control authorization model to maintain application security and implement federated identity.
Claims-based authentication is the process of authenticating a user based on a set of claims about its identity contained in a trusted token.
In ADFS, identity federation is established between two organizations by establishing trust between two security realms. A federation server on one side (the Accounts side) authenticates the user through the standard means in Active Directory Domain Services and then issues a token containing a series of claims about the user, including its identity. On the other side, the Resources side, another federation server validates the token and issues another token for the local servers to accept the claimed identity. This allows a system to provide controlled access to its resources or services to a user that belongs to another security realm without requiring the user to authenticate directly to the system and without the two systems sharing a database of user identities or passwords.
In practice this approach is typically perceived by the user as follows:
<ul>
<li>
The user logs into their local PC (as they typically would when commencing work in the morning)
</li>
<li>
The user needs to obtain information on a partner company’s extranet website - for example to obtain pricing or product details
</li>
<li>
The user navigates to the partner company extranet site - for example: <a href="http://example.com" rel="noopener nofollow ugc">http://example.com</a>
</li>
<li>
The partner website now does not require any password to be typed in - instead, the user credentials are passed to the partner extranet site using AD FS
</li>
<li>
The user is now logged into the partner website and can interact with the website ‘logged in’
</li>
</ul>
From <a href="https://en.wikipedia.org/wiki/Active_Directory_Federation_Services" rel="noopener nofollow ugc">https://en.wikipedia.org/wiki/Active_Directory_Federation_Services</a>
<hr>
Source : [Server Fault](<a href="http://example.com" rel="noopener nofollow ugc">http://example.com</a>](<a href="http://example.com" rel="noopener nofollow ugc">http://example.com</a>)

ayi_2

<blockquote></blockquote>
For a non-Microsoft person, what is ADFS?
ADFS is Microsoft’s solution for Single Sign On and web based authentication.
It is used primarily to provide a single set of credentials that can access a variety of sites not necessarily hosted within the same domain.
<blockquote></blockquote>
How does it differ to things like LDAP?
LDAP:
<ul>
<li>
Communicates using TCP/UDP on port 389 (or port 636 for LDAPS)
</li>
<li>
Contains commands for searching/retrieving/adding/deleting/modifying users, profiles and other directory entries
</li>
<li>
Can not be performed directly by a web browser, however HTTP authentication can be translated to LDAP using things like Apache’s <code>mod_authnz_ldap</code>.
</li>
<li>
When used for third-party website authentication, requires that username & password are provided to the third-party, which is not ideal for security.
</li>
<li>
Is more of an open standard and has numerous Linux implementations.
</li>
</ul>
ADFS:
<ul>
<li>
Better designed for the web as it communicates over standard HTTPS
</li>
<li>
Follows a safer process similar (but not exact) to OAuth where the original username/password are provided directly to the organisation’s ADFS server (or a proxy, but not the third-party), which if valid, returns a unique token that can be used to access a third-party website.
</li>
<li>
Although it does use make use of some open standards (HTTPS, SAML etc.) it is Microsoft-specific and requires Internet Information Services (IIS) which only runs on Windows Servers.
</li>
</ul>
See also <a href="https://stackoverflow.com/questions/28683739/ldap-vs-adfs-single-sign-on">this answer</a> on the subject.
<blockquote></blockquote>
How does it work? What kind of information would be included in a typical request to an ADFS server? Is it designed for both authentication and authorization?
It works by having a single site (site A) that hosts the ADFS / ADFS proxy servers, which has access to the credentials (usually by communicating with an Active Directory Domain Controller). It is then given a trust between other sites (sites B & C) that require authenticating through the ADFS.
When a user attempts to access site B in their browser, the site redirects the user to the ADFS-proxy website (site A) which asks for their username & password, authenticates them, returns a set of cookies for remembering them, and redirects them back to the site B, along with an access token.
If the user then attempts to visit site C, they will also get redirected to site A for authentication from the ADFS-proxy website. If the right cookies exist, the user will not be required to enter their password again, but get instantly redirected back to site C with a token.
The ADFS can be configured with specific claims (or permissions) for the user, for authorization purposes. So it can serve both roles. (Note the <a href="https://serverfault.com/questions/57077/what-is-the-difference-between-authentication-and-authorization">difference between authentication and authorization</a>.)
Some people prefer not to use it for authorization but instead keep the permissions management in the third-party website. The obvious downside is that both site A & B need to keep track of user accounts, while in the scenario where ADFS handles both, only the ADFS needs to be aware of the users.
<blockquote></blockquote>
Are ADFS servers typically accessible from the internet (whereas corporate AD domain controllers would not be)?
Yes, nearly always. ADFS is based on the notion that it will be primarily used for website authentication. And is built around IIS.
The ADFS-proxy site is the one that is usually accessible from the internet. However the ADFS itself is not. The ADFS is generally a separate server from the ADFS-proxy.
<ul>
<li>ADFS Server</li>
</ul>
Server that links to the credentials, and has the claims configuration as well as the trusts. Generally not publicly accessible.
<ul>
<li>ADFS Proxy Server</li>
</ul>
Server that hosts the IIS instance that has the login pages for the websites requiring authentication. Communicates back to the ADFS when requiring authentication. Generally publicly accessible.