ldap-auth | Simple readonly LDAP authentication with Laravel | Identity Management library

I've setup a test solution to experiment with Ldap Authentication.

I've followed the documentation and looked into this as well, then I've setup my MyLdapAuthenticationSource in the Core project along with the package Abp.Zero.Ldap and set Configuration.Modules.ZeroLdap().UseUserPrincipalNameAsUserName = true;

When I tried to login I receive Invalid Username or Password message.

Additionally, I setup a default .NET 5 Microsoft solution to verify that I'm able to connect to the Active Directory directly and it worked as expected.

Since my 2 post about the LDAP Authentication (first post, second post), we created our own custom authentication scheme and function to connect to the application using our Active Directory credentials.

We can successfully log in the application. However, we have a second function which retrieves the group of the user in the AD. Here's the code when I'm trying to retrieve the group into a Text Field (P1_GROUP) :

All:

I have a basic program for Ldap authentication which returns a "Principal User "

• I have to program a microservice using Akka HTTP. [Done]
• The service has to run inside a docker container. [Done]
• The communication (via REST API [Done]) with this service has go over HTTPS. [TODO]

While trying to make the HTTPS GET request from the web browser:

Browser warning connection not secure

While trying to make a cURL request to the service on the server:

docker ps

PORTS

0.0.0.0:443->443/tcp

curl -v https://localhost

• TCP_NODELAY set
• Expire in 200 ms for 4 (transfer 0x5648dd24df90)
• Connected to localhost (127.0.0.1) port 443 (#0)
• ALPN, offering h2
• ALPN, offering http/1.1
• successfully set certificate verify locations:
• CAfile: none CApath: /etc/ssl/certs
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:443
• Closing connection 0 curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:443

How to configure properly the Akka HTTP's server to use HTTPS, for a given:

• .pem-File (containing the root and intermediate certificates),
• .cert file (containing the certificate for my domain),
• .key-File (containing the private key) ???

1. I concatenate the ca-certs and my-cert to a single cert-chain.pem file and together with the private key created a p12 key store with openssl.
2. I wrote the following code:

In my NodeJS server, run by PM2, I authenticate my users with a LAPD service using npm module "ldap-authentication".

I have a question similiar to LDAP authorization but more specifically to OBIEE and Microsoft AD.

As described in documentation, if I use BI Publisher I only need to create a couple of XMLP_% roles in Active Directory and grant them to users after AD authentication is set up.

My questions are:

1. Can I use similiar approach to using Analytics?
2. Am I obligated to use external store for user roles?
3. Can I use DefaultAthenticator provider for roles and grant them to Active Directory users?
4. I want to use existing tools only if possible. Which options do I have for storing roles apart from database tables?

I'm trying to build a website where employees at my company can enter their Windows Domain credentials to log in. I am running an Express backend that looks like this:

i'm using Django-ldap-auth module (Git Repo), now, considering those deployment scenario:

• The container of the web application runs in a Docker swarm environment and it can be scaled
• I can't mount ANY volume, so, config files are out of questions due to data persistance
• The config needs to live in the settings.py

How i can store the django-ldap-auth configuration that can be changed by the user directly from the frontend web application?

I was considering to use docker secrets, but with docker-py i'm unable to retrieve a created secrets data.

Does anyone has some ideas to solve this puzzle?

I'm trying to enable PLAIN authentication security over a mongodb replica shard managed with OpsManager following their documentation https://docs.opsmanager.mongodb.com/v4.0/tutorial/enable-ldap-authentication-for-group/ .

The issue I'm facing is at the automation-agent trying to get mongoS status while restarting after enabling security. Please see the error output below: