View Attach (2) Info

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
png
 ldap1.png 17.1 kB 2 14-Feb-2025 03:52 Ben Spink
png
 saml1.png 28.7 kB 1 14-Feb-2025 03:50 Ben Spink

This page (revision-4) was last changed on 14-Feb-2025 03:58 by Ben Spink

This page was created on 14-Feb-2025 03:49 by Ben Spink

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 5 changed one line
This special linking is done with the plugin's instance name. So the first instance of a plugin has a hard coded name and can't be changed. You disable that instance and make a new instance of the plugin. In its name you set it to the name of the other plugin to call plus a tilde and the instance name. So in this case its "CrushLDAPGroup~"...or "CrushLDAPGroup~SAML" where "SAML" is an instance name on the CrushLDAPGroup plugin. The first one was a blank instance name (the first plugin instance) while the second example was a named instance name of it.\\
This special linking is done with the plugin's instance name. So the first instance of a plugin has a hard coded name and can't be changed. You disable that instance and make a new instance of the plugin. In its name you set it to the name of the other plugin to call plus a tilde and the instance name. So in this case its "CrushLDAPGroup~"...or "CrushLDAPGroup~SAMLAuth" where "SAMLAuth" is an instance name on the CrushLDAPGroup plugin. The first one was a blank instance name (the first plugin instance) while the second example was a named instance name of it.\\
At line 8 changed one line
The CrushLDAPGroup plugin remains "disabled" so its not trying to process any requests. Its critical it stays disabled. Its only going to be used for validating auth when a request comes behind the scenes via inter-plugin communication from the SAML plugin.\\
The CrushLDAPGroup plugin remains "disabled" so its not trying to process any requests. Its critical it stays disabled. It's only going to be used for validating auth when a request comes behind the scenes via inter-plugin communication from the SAML plugin.\\
At line 11 changed one line
When the authentication goes through the SAML plugin, after SAML has confirmed the user, it now checks its plugin name and makes the call to the other plugin to see if it wants to add more to the plugin's auth process.
When the authentication goes through the SAML plugin, after SAML has confirmed the user, it now checks its plugin name and makes the call to the other plugin to see if it wants to add more to the plugin's auth process. if you are utilizing the SAML only does Auth, you need to turn off that checkbox temporarily, set the Cache to be -1 instead of 20, then re-enable that checkbox. otherwise you won't get the items from the LDAP plugin at all.
Version Date Modified Size Author Changes ... Change note
4 14-Feb-2025 03:58 1.804 kB Ben Spink to previous
3 14-Feb-2025 03:53 1.577 kB Ben Spink to previous | to last
2 14-Feb-2025 03:52 1.568 kB Ben Spink to previous | to last
1 14-Feb-2025 03:49 1.514 kB Ben Spink to last
« This page (revision-4) was last changed on 14-Feb-2025 03:58 by Ben Spink
G’day (anonymous guest)
CrushFTP11 | What's New

Referenced by
SAMLSSO_WebApplication

JSPWiki