Overview#Security Domain Infrastructure (SDI) and NICI are tightly related.
When eDirectory is installed a few special security objects are created.
First, the Key Access Partition (KAP) container is created underneath the Security Container. Inside the KAP container, the WX Entries is created. The KAP and WX Entries represent the NICI Security Domain for the eDirectory Tree. A server, or list of servers, are assigned to be the Key server. The Key server job is to hand out the SDI Key or TreeKey to other servers in the eDirectory Tree. Security Domain servers ("Key server") manage SDI Key or TreeKey. Any NcpServer can be configured as a Key server and therefore there can be multiple Security Domain servers Key server in a eDirectory Tree.
NICISDI Keys types The Security Domain Key is created when the first NcpServer is installed, or if there is an existing eDirectory Tree with the Security Domain Infrastructure already in the eDirectory Tree, the server retrieves the SDI Key from the WX Entries Key server during the server installation.
The Key Access Partition and WX Entries #The Key Access Partition and WX Entries don't hold a copy of the actual SDI Key. The WX Entries simply holds the Distinguished Name of ncpServer(s) in the tree (NDSPKISDKeyServerDN) which can distribute the SDI Key to other ncpServers.
Note: The NICISDI.KEY file is wrapped with each ncpServer's own Key. Therefore you should never copy or restore the NICISDI.KEY file from one ncpServer to another ncpServer, as the Keys are specific to each ncpServer.
- Universal Password
- Users secrets stored in SecretStore
- Data stored by NMAS to allow users to authenticate
- Users Private Keys created by the Novell Certificate Server
- On NetWare - SYS:\SYSTEM\NICI\NICISDI.KEY
- On Microsoft Windows - %SystemRoot%\System32\Novell\NICI\NICISDI.KEY
- On Linux/Unix - /var/novell/nici/0/NICISDI.KEY
Novell Support#Always consult Novell before you get in trouble. These are where we could find more information:
- Troubleshooting SDIDIAG and NICI Problems
- Using SDIDiag to gather specific SDKey information from servers
- Verifying and Resolving Tree Key Inconsistencies with SDIDIAG
Security Domain Infrastructure, how do they sync?#'NDSPKI:SD Key Server DN' Attribute is a multi-valued attribute contains the list of Security Domain Infrastructure servers (Key server) in the tree. There MUST be at least one server in this list.
When a server boots or when NICISDI, NICIEXT, or libniciext.so are loaded the 'NDSPKI:SD Key Server DN' attribute is read. Following this read, NICISDI, NICIEXT, or libniciext connects to each server in the list and requests any new SDI Key from each server in this list.
NOTE: Deletion of a SDI Key is NOT automatically done.NcpServer was installed on Server1 and a tree was created called MyTree. The KAP and W0 objects were created during the install and the W0 object lists who is the Key server (NDSPKI:SD Key Server DN attribute on the W0 object). In this case, since this is the first server in the tree, Server1 would be listed as the Key server via the NDSPKI:SD Key Server DN attribute on the W0 object.
When the second server (Server2) is installed into the tree, Server2 would ask Server1 to send the SDI Key. This way both Server1 and Server2 each have a copy of their own SDI Key (or Treekey). Each server holds a physical copy of a NICISDI.KEY.NICI SDI Tree Key Provider Fault Tolerance so every server would have every other server's 'NDSPKI:SD Key Server DN' Security Domain Key (SDI Key or Treekey) information from servers or to verify all servers in the tree have the same SDI Key use the SDIDIAG.
We also have compiled some examples of using SDIDIAG SwitchesNICISDI module manages the TreeKeys. SASDFM manages Session Keys between two physical boxes, typically between a client and a server.