I think the short answer is yes/no/kinda. I think there's a couple parts to this. Munge is just used to assert that you are who you say you are. You could certainly write your own auth plugin that uses perhaps the Kerberos or X509 capabilities of Redhat Identity Management. If you use Kerberos you'll need to deal with service principals and token lifespan but if you're already accustomed to doing that it might not be a big deal. Here's the docs for writing an authentication plugin http://slurm.schedmd.com/authplugins.html
The other part to this as far as user identities are concerned comes into play when using the accounting database. That's really the only account database in SLURM that would need feeding. You could write some scripts to populate your accounting database based on information in the red hat identity management database. Much of this would be site specific though, I suspect. So all the hooks are there to make this work, you'd just need the glue to pull it all together. Sent from my iPhone > On Jul 27, 2016, at 8:23 PM, Da Shi Cao <[email protected]> wrote: > > > Hello everyone, > I wonder if slurm currently support the authentication/authorization of > Redhat Identity Management? So that munge is not needed, and slurm service > access is under the control of Redhat Identity Management! > > > Best Regards > Dashi Cao
