Difference between revisions of "How Registry Interfaces With Active Directory"
| Line 1: | Line 1: | ||
| − | + | Active Directory can be used as the security manager for Fusion Metadata Registry. Configuration of this is explained [[here|xxxx]]. | |
Once the Active Directory connection to the Registry has been set up | Once the Active Directory connection to the Registry has been set up | ||
Revision as of 06:41, 31 May 2022
Active Directory can be used as the security manager for Fusion Metadata Registry. Configuration of this is explained xxxx.
Once the Active Directory connection to the Registry has been set up
- Attempt to access:
The Registry recieves an Http Servlet Request (class: HttpServletRequest) from the browser. From this request object, the username and password are passed into an Authentication token (the class is a Spring UsernamePasswordAuthenticationToken )
The Active Directory service is queried to obtain a DirContext object - This is a InitialLdapContext
Failure: With respect to bad credentials a Spring BadCredentialsException is thrown which is converted into a FusionAuthenticationException which returns a 404 for the response
HttpServletResponse
Success:
The InitialLdapContext object is created. This is used to search for an object
This object is a org.springframework.ldap.core.DirContextAdapter And contains information about the user, such as the "DN" : CN=SOAP_Adam,OU=users,OU=Registry,OU=fusion,DC=metatech,DC=external
