Apigee Edge for Private Cloud creates a system administrator (sysadmin)
user during initial installation and stores that user's encrypted credentials
in configuration files on the New Edge UI (edge-management-ui)
node. The New Edge UI uses these stored credentials to authenticate backend
requests to the Management Server. If the password or email address for your
sysadmin user changes (for example, in your external LDAP or after a password
reset), you must update the stored sysadmin credentials on the New Edge UI
node.
Change the New Edge UI sysadmin credentials
You can update the stored sysadmin credentials on the New Edge UI
(edge-management-ui) using either of the following methods:
- Run the
apigee-setuputility with theueprofile and a silent configuration file. - Encrypt the credentials with the
management-uibinary and setconf_uebe_mgmtCredentialin/opt/apigee/customer/application/management-ui.properties.
Update credentials using apigee-setup
- Edit the silent configuration file that you used to install the New Edge
UI (
edge-management-ui) to set the sysadmin and SMTP properties:ADMIN_EMAIL=newUser APIGEE_ADMINPW=newPW SMTPHOST=smtp.gmail.com SMTPPORT=465 SMTPUSER=foo@gmail.com SMTPPASSWORD=bar SMTPSSL=y SMTPMAILFROM="My Company <myco@company.com>"
You must include the SMTP properties when updating the sysadmin credentials because
setup.shresets all New Edge UI properties from the silent configuration file. - On the New Edge UI node, run the
apigee-setuputility with theueprofile to update the credentials onedge-management-ui:/opt/apigee/apigee-setup/bin/setup.sh -p ue -f configFile
Update credentials using management-ui.properties
- On the New Edge UI node, change to the
/opt/apigee/edge-management-uidirectory and encrypt the sysadmin username and password using themanagement-uibinary:cd /opt/apigee/edge-management-ui && ./bin/management-ui --encrypt 'userName:PWord'
- Open
/opt/apigee/customer/application/management-ui.propertiesin an editor. If the file does not exist, create it:vi /opt/apigee/customer/application/management-ui.properties
- In
management-ui.properties, set theconf_uebe_mgmtCredentialtoken to the encrypted value returned in Step 1:conf_uebe_mgmtCredential="STRING_RETURNED_IN_STEP_1"
- Set the owner of
management-ui.propertiestoapigee:apigee:chown apigee:apigee /opt/apigee/customer/application/management-ui.properties
- Configure and restart the New Edge UI (
edge-management-ui):/opt/apigee/apigee-service/bin/apigee-service edge-management-ui configure /opt/apigee/apigee-service/bin/apigee-service edge-management-ui restart
Test the New Edge UI configuration
- Open the New Edge UI in a browser on port 3001:
http://edge_UI_IP:3001/
For example:
http://192.168.52.100:3001/
- Log in using the updated sysadmin credentials. A successful login confirms that the New Edge UI configuration is valid.
Test the Management Server configuration
Verify that you can access the central pod on the Management Server by
running the following curl command:
curl -u sysAdminUser:password \ http://localhost:8080/v1/servers?pod=central
The Management Server returns output in the following format:
[ { "internalIP" : "192.168.1.11", "isUp" : true, "pod" : "central", "reachable" : true, "region" : "dc-1", "tags" : { "property" : [ ] }, "type" : [ "application-datastore", "scheduler-datastore", "management-server", "auth-datastore", "apimodel-datastore", "user-settings-datastore", "audit-datastore" ], "uUID" : "d4bc87c6-2baf-4575-98aa-88c37b260469" }, { "externalHostName" : "localhost", "externalIP" : "192.168.1.11", "internalHostName" : "localhost", "internalIP" : "192.168.1.11", "isUp" : true, "pod" : "central", "reachable" : true, "region" : "dc-1", "tags" : { "property" : [ { "name" : "started.at", "value" : "1454691312854" }, ... ] }, "type" : [ "qpid-server" ], "uUID" : "9681202c-8c6e-4da1-b59b-23e3ef092f34" } ]