From: Ratan Gupta <ratagupt@linux.vnet.ibm.com>
To: openbmc@lists.ozlabs.org
Subject: Re: IPMI user account with LDAP/Active Directory
Date: Thu, 12 Jul 2018 11:48:56 +0530 [thread overview]
Message-ID: <b50089f7-52be-fff7-7c53-9e11dc7c5baa@linux.vnet.ibm.com> (raw)
In-Reply-To: <dd593784-d650-0393-0e44-3f6a5bcbdfec@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
Hi Tom.
> As IPMI requires clear text password my understanding is that LDAP/AD
is not suitable for IPMI user account management.
Is the purpose of LDAP/AD to support authentication from UI along with
IPMI user accounts on the BMC?
Also LDAP/AD cannot be used for IPMI session setup as passwords are
stored as one-way hash and cannot be retrieved.
Seems ldap gets the way through which we can access the password.
e.g.
|sudo ldapsearch -H ldapi:// -LLL -Q -Y EXTERNAL -b "cn=config"
"(olcRootDN=*)" dn olcRootDN olcRootPW Regards Ratan Gupta |
On Tuesday 10 July 2018 12:44 AM, Tom Joseph wrote:
> Hello,
>
> I came across the user guide of MegaRAC, SuperMicro etc mentioning
> about the LDAP/Active directory settings.
> (Example:
> https://argonsys.com/learn-microsoft-cloud/articles/supermicro-ipmi-active-directory-integration/)
>
> As IPMI requires clear text password my understanding is that LDAP/AD
> is not suitable for IPMI user account management.
> Is the purpose of LDAP/AD to support authentication from UI along with
> IPMI user accounts on the BMC?
> Also LDAP/AD cannot be used for IPMI session setup as passwords are
> stored as one-way hash and cannot be retrieved.
>
> Any thoughts?
>
> Regards,
> Tom
>
[-- Attachment #2: Type: text/html, Size: 2079 bytes --]
prev parent reply other threads:[~2018-07-12 6:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 19:14 IPMI user account with LDAP/Active Directory Tom Joseph
2018-07-12 6:18 ` Ratan Gupta [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b50089f7-52be-fff7-7c53-9e11dc7c5baa@linux.vnet.ibm.com \
--to=ratagupt@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).