IdentityServer4.LdapExtension | IdentityServer4 Ldap Extension | Identity Management library
kandi X-RAY | IdentityServer4.LdapExtension Summary
kandi X-RAY | IdentityServer4.LdapExtension Summary
IdentityServer4 Ldap Extension (OpenLdap or ActiveDirectory).
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of IdentityServer4.LdapExtension
IdentityServer4.LdapExtension Key Features
IdentityServer4.LdapExtension Examples and Code Snippets
Community Discussions
Trending Discussions on IdentityServer4.LdapExtension
QUESTION
I'm creating an SSO server, to centralize all users in ActiveDirectory(AD) and manage them there instead of the database of each specific application.
To made this server I used IdentityServer4(Idsr4) with Ldap/AD Extension
I've setted the Idsr4 to use identity based on AD (this is "centralized identity"), and users now can login on Idsr4 with own AD login/ password
The question now is how to map the centralized identity to applications. I want to use same identity user in several applications.
I read through the documentation of IdentityServer4 but could not find anything related to a proposed structure.
Does anybody have a clear structure setup which could be used to understand the whole setup? (Separation like Asp.Net MVC Boilerplate, IdentityServer4, Protected Api.)
IdentityServer4 Config:
...ANSWER
Answered 2019-Apr-27 at 03:51I think the GrantType.ResourceOwnerPassword
flow doens't support AD
login and not support by the UseOpenIdConnectAuthentication
neither , you can use Implicit
or Hybrid
flow.
Once you authenticate the to your client mvc app, you can view any claims in HttpContext.User
and find the correct claim value as user's identity (they are just claims , and no need to create a local account)
QUESTION
I'm currently working on a project where I'm trying to set up a service based on IdentityServer4 (https://github.com/IdentityServer/IdentityServer4) that authenticates users by querying a local Active Directory via LDAP.
To achieve that, I also included the IdentityServer4.LdapExtension (https://github.com/Nordes/IdentityServer4.LdapExtension) in my project. The working example from the repository works fine (https://github.com/Nordes/IdentityServer4.LdapExtension/tree/master/Sample/IdentityServer) - but the custom logic is part of the UI, and I need my service to operate without any UI.
Simply adding
...ANSWER
Answered 2018-Sep-07 at 20:30From your question it sounds like you already have a username
and password
. Note client_id
!= username
and client_secret
!= password
. client_id
is the identity for a client application.
The grant type you are trying to use is called Resource Owner Password when using the authorize endpoint or password when using the token endpoint. This grant type is used to support legacy systems and is not recommended for new development.
The code that you want to executed to authenticate a user is in LdapUserResourceOwnerPasswordValidator.cs and it should be executed if you pass the correct parameters to the token endpoint:
POST /connect/token
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install IdentityServer4.LdapExtension
Ldap Extension 2.0.0 goes with IdentityServer 2.2.x
Ldap Extension 2.1.7 goes with IdentityServer 2.3.x
Ldap Extension 2.1.8 goes with IdentityServer 2.4.x
Ldap Extension 3.1.0 goes with IdentityServer 4.1.2
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page