How Does OS User Application authentication work with the Central Credential Provider?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Secrets Management Articles
2 min read
L1 Bithead
No ratings

Question

How is OS User authentication different between the local credential provider and the Central Credential Provider web service?

Answer

The CCP uses a different mechanism than the local provider to capture the OS user. The difference has more requirements and more limited use cases.

On the local provider when using OS user as an application authentication restriction the provider uses the process ID of the calling application to look up which user started the process in the process table. At a high level this is the same process for local providers on both Windows and *Nix variants.

On the CCP OS user is captured using an IIS function known as Windows authentication. On a human interactable web site when opening a new session Windows Authentication will bring the end user to their desired page hosted on IIS without being prompted for a username and password.

The way this works is that when the end user accesses an Windows Authentication protected website their local authentication token is passed to IIS which then verifies the token is valid with Active Directory.

Windows Authentication has more requirements:
  1. The system making the call to the CCP must be on the same domain as the CCP server
  2. The user whose name is specified as OS User must have a domain session on the host they are making the call from. The call must come from this session.
  3. The method/language making the call to the CPP must support passing the authentication token.
  4. Anonymous Authentication may need to be disabled. (this will restrict the CCP application to only allow Windows Authentication calls)
In power shell and .Net the “UseDefaultCredentials” property will send the users authentication token when making a REST call.

An example rest call in PowerShell that will forward the session token of the user executing the command
 
invoke-webrequest -method GET -UseDefaultCredentials -ContentType application/json -uri https://pvwa.taco.day/AIMWebService/api/Accounts?AppID=dave"&"username=bear


 
Rate this article: