| |
Results |
|
DA: Configuring LDAP in DA based upon an existing Dimensions LDAP Configuration
|
When an existing configuration of Dimensions CM exists and is using LDAP for authentication, it may be desirable to configure Deployment Automation to utilize the same Dimensions LDAP server. Many of the LDAP configuration settings may be copied or somewhat modified and copied from the dm.cfg file into the LDAP configuration sheet of DA.
|
|
|
|
DA: LDAP authentication returns: Invalid username or password
|
I’m trying to connect DA to an LDAP service for authentication. I’m able to import LDAP users, but when I try to login as them, I just receive “Invalid username or password”.
|
|
|
|
DA 6.3.3 : Does "Deployment Automation User Login" support Windows 2016 Active Directory?
|
There is no specific statement anywhere that mentions this. However one of the authentication methods supported in DA is via the LDAP protocol and Windows 2016 Active Directory should be compatible with this.
|
|
|
|
DA: Mistakenly edited Internal Security/Internal Storage Authentication Realm and now cannot login
|
In order to configure DA for LDAP authentication, a new authentication realm should be added. From time to time, some folks will mistakenly edit the "Internal Security/Internal Storage" realm and attempt to use it for the LDAP realm. This may leave DA in a configuration where no one is able to log in.
|
|
|
|
DA: Component Versions show "Created by" as wrong user
|
This means that the value in "Created By" has nothing to do with system security, nor LDAP nor domain users. It is usually the user that was specified as the DA internal admin at the time that DA was installed. By default this username would be admin.
|
|
|
|
DA: How to get more information about automatic DA user and group creation in the log files
|
2019-05-02 09:21:39,473 - Search found User DN: cn=vince,ou=Dim,o=support,dc=serena,dc=com 2019-05-02 09:21:39,473 - LDAP Group Definition: Search 2019-05-02 09:21:39,473 - LDAP Group Search: member=cn=vince,ou=Dim,o=support,dc=serena,dc=com
|
|
|
How to Move DA Server to new Hardware and Optionally Upgrade to a new Release
|
9) The first time Tomcat and DA successfully start and connect to the database, DA will upgrade the schema. 10) If your old server had any certificates loaded for access to a secure LDAP server, or component sources (such as MAVEN or NEXUS, etc.), you will need to load those certificates into the JRE certificates database on the new machine. 11) If your old server was configured for SSO, you may have to locate the pages in the documentation and complete the SSO configuration for the new server.
|
|
|
|
Checking DA Agent Status
|
For REST methods other than “GET”, a browser plugin may be necessary to execute the call. It is also possible to use curl for the REST calls, although the authentication syntax may vary based upon whether your system is using local users, LDAP , SSO, and whether or not SSL is required for login, etc..
|
|
|
|
12.2.0.3 / connection to ldaps is failing / OpenSSL error error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure
|
20120606 090254.511 t1cb8 IO bf16:4d ### ERR handle EIOSSLREAD 4 da 80 10.194.0.35:10396 ukwn Trouble processing events for fd=318080 (e.g. i/o error). Will drop connection.
|
|
|
|
DA: Getting "Could not restore PropSheet" errors/warnings in deployserver.out
|
2018-10-09 09:14:53,154 - Could not restore PropSheet for PropSheetGroup by handle resources/395de0c2-0853-4f9f-a654-e69 ad 8646ef1/propSheetGroup /propSheets/53d6b040-7c53-48a8-ac24-882a59b99fa9.-1
|
|
|
