IDConsole does not have the concept of plugins like iManager, either it is included or not, right now.  Maybe that will change.

Someone made the brilliant idea of only show the abilities of the directly connected server.

Thus when you log in, you specify a tree name or server name (should be DNS resolvable and match a SAN in the SSL cert) and you connect to a single server over LDAP.

iManager used NCP and LDAP, which allowed it to tree walk as needed over NCP.  IDConsole is more focussed on one server ata time.

If there is not driver set associated to the server you logged into, then you will not see the tiles for IDM Management, even if there is IDM in the tree. Which I think is a bad decision.

So when you log in, point at one of the servers that has the driver set and they should show up.

Also, iManager does continue to work. What does not work is installing it on the same server as eDirectory due to conflicting libraries.  So pick a standalolne machine for iManager and it is still mostly good. (Take care!  Some things won't wokr or will break.)

Thank you, I must be missing something.    The IDM engine and the AD Driver I need is running on a Windows server. I configured and run the Identity Console Windows build directly from the desktop of that same IDM server.  I login to that Identity Console using the IP address *OR* DNS Name of the same server, and I am able to login correctly and browse the tree and see things in the eDirectory section.  But there must be something missing for it to detect and offer the Identity Manager options, because it does not show up.      I can also login to a different iDentity Console running on an OES 24.x server, also don't see any IDM stuff.  But on that login screen, if I point the server to the IDM server directly I cannot login, I get invalid credentials.

For iManager, yes the iManager instance that was used (and installed) for IDM was on that same Windows server, and it won't run at all.   I have other instances of iManager in the tree on OES servers and will see if I can get the IDM plugins installed.  I just need to be able to control/start/stop the driver, it doesn't seem to be running.

. 

Two issues:  1) Why cannot I not login to a server as a target, for IDConsole from one, but not the other?  2) Why I cannot see the IDM options.

For #1, the LDAP Server object on each server, select a Certificate that you have created custom, not the default one, to set as the LDAP Servers SSL certificate.

That special cert you make, has to include Subject Alternate Name extensions. Add the DNS name of the server.  Add the IP Address of the server.  Add the DNS name of the tree.  I forget if you can do DNS names that are incomplete, like simply MY-Tree instead of my-tree.acme.com.

Add all those, and do it for all your servers, since the cert is server by server, and set LDAP to use them.  This is because security people got really uptight about attacks on SSL/TLS.  So now the URL you connect to must match the SAN in the cert.

Java enforces this, other API's do as well (since I do ont think IDConsole is using Java at all). 

Then you should be able to user any server configured this way from any IDConsole instance.  (Issue is in the tree, not the IDConsole install).