| LDAP roles as parameters to scripts [message #902805] |
Mon, 20 August 2012 10:15  |
Harald van Kesteren Messages: 2 Registered: July 2009 Location: Netherlands |
Junior Member |
|
|
I'm using hudson v2.2.0 as a tool for build and deploy. Currently the authentication/authorisation is controlled by hudson's internal user-database. This has to change : LDAP has to be used for this in the future.
Some procedures (shell-scripts) use the HUDSON_USER environment variable to control parts of the flow (a bit wacky, I know). The fastest way to 'transform' the processes is to use the LDAP-roles for the same purpose (or is it?).
Question: how do I get the scripts to identify which role (or roles) the user has?
The LDAP authentication can control hudson, can information resulting from that be passed on to shell-scripts that are run by the hudson-jobs?
That's All Folks,
Harald.
|
|
|
|
| Re: LDAP roles as parameters to scripts [message #905323 is a reply to message #904222] |
Thu, 30 August 2012 03:06  |
Harald van Kesteren Messages: 2 Registered: July 2009 Location: Netherlands |
Junior Member |
|
|
Winston,
Thanks for your answer. The 'standard environment variables' I already was aware of. What you sketch (building my own hudson plugin) might be an option for the future, but is way to advanced for this moment .
We have implemented a kind of workaround (or maybe it is just the right way to do it!) by having a set of hudson-jobs for each LDAP authorisation group. These are tuned to the use for that group. That way there is no need for passing on the LDAB-group name to the underlying scripts.
That's All Folks,
Harald.
|
|
|
Powered by
FUDForum. Page generated in 0.09357 seconds