
•
The domain controller addresses configured in iDRAC does not match the Subject or Subject Alternative Name of the directory
server certificate. If you are using an IP address, read the next question. If you are using FQDN, make sure you are using the
FQDN of the domain controller and not the domain. For example,
servername.example.com
instead of
example.com
.
Certificate validation fails even if IP address is used as the domain controller address. How to resolve this?
Check the Subject or Subject Alternative Name field of your domain controller certificate. Normally, Active Directory uses the host
name and not the IP address of the domain controller in the Subject or Subject Alternative Name field of the domain controller
certificate. To resolve this, do any of the following:
•
Configure the host name (FQDN) of the domain controller as the
domain controller address(es)
on iDRAC to match the Subject
or Subject Alternative Name of the server certificate.
•
Reissue the server certificate to use an IP address in the Subject or Subject Alternative Name field, so that it matches the IP
address configured in iDRAC.
•
Disable certificate validation if you choose to trust this domain controller without certificate validation during the SSL
handshake.
How to configure the domain controller address(es) when using extended schema in a multiple domain environment?
This must be the host name (FQDN) or the IP address of the domain controller(s) that serves the domain in which the iDRAC
object resides.
When to configure Global Catalog Address(es)?
If you are using standard schema and the users and role groups are from different domains, Global Catalog Address(es) are required.
In this case, you can use only Universal Group.
If you are using standard schema and all the users and role groups are in the same domain, Global Catalog Address(es) are not
required.
If you are using extended schema, the Global Catalog Address is not used.
How does standard schema query work?
iDRAC connects to the configured domain controller address(es) first. If the user and role groups are in that domain, the privileges
are saved.
If Global Controller Address(es) is configured, iDRAC continues to query the Global Catalog. If additional privileges are retrieved
from the Global Catalog, these privileges are accumulated.
Does iDRAC always use LDAP over SSL?
Yes. All the transportation is over secure port 636 and/or 3269. During test setting, iDRAC does a LDAP CONNECT only to isolate
the problem, but it does not do an LDAP BIND on an insecure connection.
Why does iDRAC enable certificate validation by default?
iDRAC enforces strong security to ensure the identity of the domain controller that iDRAC connects to. Without certificate
validation, a hacker can spoof a domain controller and hijack the SSL connection. If you choose to trust all the domain controllers in
your security boundary without certificate validation, you can disable it through the Web interface or RACADM.
Does iDRAC support the NetBIOS name?
Not in this release.
Why does it take up to four minutes to log in to iDRAC using Active Directory Single Sign–On or Smart Card Login?
292
Содержание iDRAC 7
Страница 1: ...iDRAC 8 7 v2 40 40 40 User s Guide ...
Страница 108: ...For more information see the iDRAC RACADM Command Line Interface Reference Guide available at dell com idracmanuals 108 ...
Страница 268: ...By default the logs are available at Event viewer Applications and Services Logs System 268 ...