There continues to be a fair amount of confusion (or miscommunication on our part) around Access Manager, Delegated Administrator, and schema choice. And the same confusion potentially could exist when it comes to deploying Comms Suite 5. So, here in a nutshell, are what I think are the basic questions and answers surrounding these products. I'll try and keep track of these issues going forward and continue to post them.
- In Communications Suite 5, does Delegated Administrator 6.4 still require you to deploy Access Manager?
Yes, Delegated Administrator 6.4 still requires you to deploy Access Manager.
- In Communications Suite 5, does Communications Express 6.3 require you to deploy Access Manager?
Starting with the Communications Suite 5 release, this dependency on Access Manager for Schema 2 has been removed.
In previous releases, Communications Express used the following APIs and libraries to establish connections and fetch information from an LDAP store:
- Domain MAP API (which a part of Communications Express) if Communications Express was deployed using Schema 1 mode.
- Access Manager SDK if Communications Express was deployed using Schema 2
This made Communications Express dependent on Access Manager in Schema 2 mode even though Access Manager is not mandatory for it to work apart from just connecting and fetching information from the LDAP store.
- When do I need to deploy Schema 2? Do I only need Schema 2 in an Access Manager/Delegated Administrator situation?
Delegated Administrator currently supports only Schema 2. Other situations requiring Schema 2 include integration with Portal Server, and with Access Manager (for SSO).
For more information on these topics, see my previous entry