X
Try Oracle Cloud Platform For Free

Virtual Directory & Sun Directory Proxy Server

Directory Master Event 09 in New Jersey

Last week, I attended the Sun Directory Master Conference in SomerSet, NewJersey. I gave a presentation about the next major revision of Sun Directory Proxy...

Last week, I attended the Sun Directory Master Conference in SomerSet, NewJersey. I gave a presentation about the next major revision of Sun Directory Proxy Server 7.0.It was also a unique opportunity to meet with Sun Partners and discuss Identity and Directory deployments. 

cn=Directory Manager access through the proxy

Many DPS users reported the following problem: Bind requests as cn=Directory Manager fails when the proxy is deployed. DPS analyses the bind dn to route the...

Many DPS users reported the following problem: Bind requests as cn=Directory Manager fails when the proxy is deployed. DPS analyses the bind dn to route the request to the data view holding the target dn. In many configuration, there is no data view candidate configured to hold the cn=directory manager suffix. There are 2 ways to address the problem: Either create a additional data view with view base set to "cn=directory manager" or use "implicit" routing with a data view...

DSEE 6.3.1 has been released

Sun Directory Services Enterprise Edition (DSEE) 6.3.1 has been released.Release notes and download informations are available...

Sun Directory Services Enterprise Edition (DSEE) 6.3.1 has been released.Release notes and download informations are available at http://docs.sun.com/app/docs/doc/820-5817

Forum about LDAP, Sun Directory, Proxy Server and Virtual Directory

If you have some questions about Sun Directory Server Edition, Directory Proxy and Virtual Directory or you want to share best practices, don't hesitate to use...

If you have some questions about Sun Directory Server Edition, Directory Proxy and Virtual Directory or you want to share best practices, don't hesitate to use the Sun Developer Forum dedicated to these products. See you there!

Fail-over based on the directory server operational state

DPS 6.x load-balancing / fail-over can be configured to stop sending traffic to a specific directory server instance in maintenance, even when that instance is...

DPS 6.x load-balancing / fail-over can be configured to stop sending traffic to a specific directory server instance in maintenance, even when that instance is up and running. For instance, you may want to remove a directory server instance from the mesh while an import or re index is in progress. DPS 6.x periodically checks each ds server for availability by issuing (amongst others) a search request. A directory server instance is considered unreachable when that search...

DPS 6.3 properties that require server restart

The list of  DPS 63 config changes that require a restart is part of Admin guide.  Chapter 18: Directory Proxy Server Instances / Configuring Directory Proxy...

The list of  DPS 63 config changes that require a restart is part of Admin guide.  Chapter 18: Directory Proxy Server Instances / Configuring Directory Proxy Server Instances /  Configuration Changes Requiring Server Restart http://docs.sun.com/app/docs/doc/820-2763/gbong?l=en&a=view This list will be greatly reduced in the next release (7.0) 

DIT changes with dn virtual transformations

Here is a summary of a common deployment scenario with Sun Directory Proxy Server: LDAP entries are grouped by location in the DIT, e.g user entries are located...

Here is a summary of a common deployment scenario with Sun Directory Proxy Server: LDAP entries are grouped by location in the DIT, e.g user entries are located under ou=north,ou=people,dc=company, dc=com or  ou=south,ou=people,dc=company, dc=com or ou=east,ou=people,dc=company, dc=com or ou=west,ou=people,dc=company, dc=com based on user physical location. Later, for sake of simplicity, the DIT is flatten so that every user entry is stored immediatly under ou=people,...

About rootDSE again

For monitoring purpose, a customer needs to get access to the rootDSE entry of each directory server behind DPS. By default, DPS manages the rootDSE itself so...

For monitoring purpose, a customer needs to get access to the rootDSE entry of each directory server behind DPS. By default, DPS manages the rootDSE itself so that (in a virtual context) it reflects all the naming contexts and capabilities exposed by the proxy. Here is one way to have access to the rootDSEs in question:- the rootDSE DS content is exposed through a data view dedicated to ds monitoring. This dataview view base is choosen to not conflict with any suffix used by...

RootDSE entry management with DPS 6.x

By default, the rootDSE entry is managed/returned by the directory proxy itself and reflect proxy LDAP capabilities. Such behaviour is mandatory whenever...

By default, the rootDSE entry is managed/returned by the directory proxy itself and reflect proxy LDAP capabilities. Such behaviour is mandatory whenever virtualization is in use so that underlying data layout is hidden from the client applications. In some specific cases, it might be interesting to configure DPS to fetch the rootDSE entry from the directory server(s) itself. Here is the procedure: 1- Create a data view (rootDSE) with view base set to "" and associate a data...