The FlexDeploy HTTP Agent distribution contains the following components:
A tomcat 9 Tomcat 9 server with required libraries, and base configurations
The HttpAgent WAR
...
Setting JAVA_HOME in the configuration will be done later. This Java will be used to run the tomcat Tomcat server. A different Java version can be specified on the endpoint configuration in FlexDeploy and those will be used to actually execute plugins.
...
For basic configuration only, the password needs to be configured in the given HTTPS_AGENT_HOME/apache-tomcat-flexdeploy-https-agent/conf/tomcat-users.xml file. Here’s what that will look like:
...
| Code Block | ||
|---|---|---|
| ||
<!-- Use the LockOutRealm to prevent attempts to guess user passwords
via a brute-force attack -->
<Realm className="org.apache.catalina.realm.LockOutRealm">
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<!--<Realm
className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase" />-->
<!-- user MUST be a part of FlexDeployHTTPSAgent group in order for authentication
to work -->
<Realm className="org.apache.catalina.realm.JNDIRealm"
connectionName="CN=administrator,CN=Users,DC=flexagondev,DC=local"
connectionPassword="password"
connectionURL="ldap://yourldapurl.example:389"
userBase="CN=Users,DC=flexagondev,DC=local"
userSearch="(&(objectClass=*)(sAMAccountName={0}))"
userRoleName="member"
roleBase="CN=Users,DC=flexagondev,DC=local"
roleName="cn"
roleSearch="(objectClass=group)"
/>
</Realm> |
Next you can , add your the organization specific LDAP/Azure Directory configuration.
Make sure the user you are trying to connect as with has the FlexDeployHTTPSAgent role or they will not be able to connect.
...