Unable to assign port 80 & 443 to http & https respectively in OHS, which is running on Linux environment. Below error logged in OHS logs
[VirtualHost: main] (13)Permission denied: make_sock: could not bind to address [::]:443
On a UNIX system the TCP/IP port numbers below 1024 are special in that only processes with root privileges are allowed to listen on those ports. Continue reading “How to assign a Privileged Port to OHS”
User getting error “java.security.AccessControlException: access denied (“javax.management.MBeanTrustPermission” “register”)” while running “idmConfigTool.sh -configOIM input_file=OIMconfigPropertyFile” for OAM-OIM integration. Continue reading “OIM 11gR2PS3 : Error “java.security.AccessControlException: access denied (“javax.management.MBeanTrustPermission” “register”)” while integrate OAM – OIM”
Error while starting OAM servers in clustered environment. Below error has been logged while starting up the servers.
(thread=Cluster, member=n/a): This member is not authorized to join the cluster. Rejected by Member(Id=1, Timestamp=2017-06-29 12:53:04.123, Address=192.168.24.12:9095, MachineId=1901, Location=site:lda,machine:OAMHOST01,process:916, Role=WeblogicServer).>
(thread=[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)
All the nodes must have a valid and identical Well Known Address (WKA) list. An empty WKA list will prevent the nodes from forming a cluster. Continue reading “OAM : Error while starting servers – Failed to start Service “Cluster” (ServiceState=SERVICE_STOPPED, STATE_JOINING)”
Error “SecurityProvider service class name for OAMIDAsserter is not specified” while starting managed server from weblogic admin console. Node manager is up and running.
Below has been logged in managed server log
Continue reading “Unable to start managed server using Nodemanager – SecurityProvider service class name for OAMIDAsserter is not specified.”
We have integrated OAM-OIM-OUD. LDAP Sync has been enabled between OIM and OUD.
When we create an user in OIM , it creates user in OUD without password management objectclass and attributes like oblogintrycount / obpasswordchangeflag / obpasswordexpirydate. Continue reading “OIM – OUD Ldap sync – attributes like obpasswordchangeflag, obpasswordexpirydate not created”
Using below steps we can change/modify logo in default OAM login page.
To update, logo, we need to replace login_logo.png from oam_server and oam_admin deployments. Continue reading “Change logo in default OAM login Page”
OIM Users are not created after running the Active Directory User Trusted Recon scheduled job.
The following message is displayed In the reconciliation event generated for the user:
‘Data Validation Failed’ as the current status and ‘Invalid ManagerLogin : <Manager ID>’. Continue reading “OIM : AD – OIM trusted reconciliation with error “Data Validation Failed : Invalid ManagerLogin : “”