If you need the script please just let me know I have version 1.4 and 1.5 as needed.
I recommend running this script if you have services that are failing to start due to authentication, or if you suspect an issue with the Common Proxy User, such as missing user or incorrect password.
The Common Proxy Repair script checks and fixes all aspects of the Common Proxy user including:
Executing this script on a working system is not harmful as long as the correct user is selected/specified.
See /var/log/common-proxy-fix.log for debug messages
Usage: common-proxy-fix-1.0.sh -u ADMIN_DN [options]
-u ADMIN_DN Admin username in LDAP syntax (required)
-w ADMIN_PASS Admin password
-h LDAPS_IP LDAPS IP, default is 127.0.0.1
-p LDAPS_PORT LDAPS port, default is 636
-f SERVICE_LIST Comma separated list of services to force config for CASA
Example: common-proxy-fix-1.0.sh -u cn=admin,o=org
Example: common-proxy-fix-1.0.sh -u cn=admin,o=org -w P@ssw0rd
Example: common-proxy-fix-1.0.sh -u cn=admin,o=org -h 192.168.2.5 -p 1636
Example: common-proxy-fix-1.0.sh -u cn=admin,o=org -f cifs,dns,dhcp
pluto:~ # common-proxy-fix-1.0.sh -u cn=admin,o=mf
Logging to /var/log/common-proxy-fix.log . . .
Enter password for cn=admin,o=mf:
Verifying authentication for ADMIN_DN....SUCCESS
Retrieving Common Proxy username and password....SUCCESS....cn=OESCommonProxy_pluto,ou=servers,o=mf
Retrieving CIFS username and password............SUCCESS....cn=admin,o=mf
Retrieving AFP username and password.............SUCCESS....cn=OESCommonProxy_pluto,ou=servers,o=mf
Retrieving DNS username and password.............SUCCESS....cn=OESCommonProxy_pluto,ou=servers,o=mf
Retrieving DHCP username and password............FAILURE
Retrieving LUM username and password.............SUCCESS....cn=OESCommonProxy_pluto,ou=servers,o=mf
/etc/opt/novell/proxymgmt/proxy_users.conf is empty
1) Default Common Proxy User: cn=OESCommonProxy_pluto,ou=servers,o=mf (in eDir)
2) Common Proxy set in CASA: cn=OESCommonProxy_pluto,ou=servers,o=mf (in eDir)
3) Common Proxy set in CONF:
4) Enter Common Proxy Username
Select the correct CP Username (1/2/3/4/q): 2
Checking Common Proxy UP Policy....SUCCESS
Verifying authentication with the existing common proxy password....SUCCESS
Assigning Common Proxy User to Common_Proxy_Policy....SUCCESS
Adding user to /etc/opt/novell/proxymgmt/proxy_users.conf....SUCCESS
Checking Crontab for change_proxy_pwd.sh....SUCCESS
Setting credentials for cifs....username does not match
Setting credentials for afp....ALREADY SET
Setting credentials for dns....ALREADY SET
dhcp is installed, but credentials were not found.
Force dhcp credentials into CASA using CASAcli? (y/n): y
Forcing CASA credentials for dhcp using CASAcli....SUCCESS
Not setting credentials for ifolder....not installed
Not setting credentials for netstorage....not installed
Not setting credentials for ncs....not installed
Setting credentials for lum....ALREADY SET
Log File: /var/log/common-proxy-fix.log
Is this script still available? I cannot see it for download on the page.
I will review the logic for the script, but I'm not sure there will be an easy way for the script to know if the Common Proxy user is properly configured when assigned to a non-default Universal Password Policy.
My customer has been using this script to fix Common Proxy User issues. However; they have a Common Proxy Policy for each site so for example, Common_ Proxy_policy.Sitename.region.tree so when the script runs it attempts to put the user back in the top level Policy, and we would like to keep it in the site policy. Is that possible.