You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
is it possible to get the original password for scripting in the Event Notification state when using the singleUser Plugin.
I have authentication and Authorization against an LDAP Server, then i want all those users use a single local mandatory profile.
Until now this is working fine.
But i also want to use the original credentials used to authorize in a logon script of the user context to map some drives. But as far as i can see i can only get the original username.
I could work arround this by have the password stored somewhere in the authentication stage but this seems very insecure to me. Any idea if im missing something?
Thanks!
The text was updated successfully, but these errors were encountered:
http://mutonufoai.github.io/pgina/documentation/plugins/single_user.html
By using this plugin pGina is unable to verify a user during logon as shown here. Pgina can’t detect a loggin off session from this user nor if this user is already logged in and tries to unlock the user. As you can see the Username Modification Plugin runs in stage 3 while the above checks are done in stage 2. Also plugins registered for Notification Events won’t work properly.
It was a terrible idea from the original developers to add this plugin.
What you want leads to a disaster.
Let your users know the user you want to be used on this system, right now they can login anyway.
Problem solved.
Hi,
is it possible to get the original password for scripting in the Event Notification state when using the singleUser Plugin.
I have authentication and Authorization against an LDAP Server, then i want all those users use a single local mandatory profile.
Until now this is working fine.
But i also want to use the original credentials used to authorize in a logon script of the user context to map some drives. But as far as i can see i can only get the original username.
I could work arround this by have the password stored somewhere in the authentication stage but this seems very insecure to me. Any idea if im missing something?
Thanks!
The text was updated successfully, but these errors were encountered: