OpenAM 14.6.4 configuration on WebSphere 9

[JDevsWork]

Hello! I am having some problems with getting OpenAM to configure correctly in a non local environment. We are trying to add this to an existing WebSphere ecosystem. I've created a new keystore with the IBM Java that we are using with the WAS instance, and repacked the war with that. These options have been set on the WAS JVM: -DamCryptoDescriptor.provider=IBMJCE -DamKeyGenDescriptor.provider=IBMJCE -Xmx4096m. We gave it a lot more memory than it needs, just to be sure there wasn't any issue with that. My local machine is running WebSphere Application Server 9.0.5.121 and the servers are running WebSphere Application Server 9.0.5.9.

On my local machine, I modified the host file to include openam.example.com, and everything works as expected. I can create a new configuration, and can access the dashboard after it's finished creating those config files.

On the hosted server, we have a FQDN setup for the application. We use the same war file that I deployed to my local machine. The app will install and start on the hosted server, and I can see the configuration screen. I noticed that after setting up the FQDN for the application, the port fields on the Configuration Store screen all default to -1 instead of having values populated. On my local machine, that screen takes a couple seconds to load and when it does all of the ports are pre populated with values (Port: 50389, Admin Port: 4444, JMX Port: 1689). I can change all of those values to what they are on my local, but the process still fails out with generally one of two errors:

12/28/2022 03:12:58:498 PM CST: Error loading OpenAM suffix 1 AMSetupServlet.processRequest: errorcom.sun.identity.setup.ConfiguratorException: emb.creatingfamsuffix.failure

or

AMSetupServlet.processRequest: errorcom.sun.identity.security.AMSecurityPropertiesException: AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.

I've double checked everything, from the war being installed down to the installation/configuration process is the same.

Should this work on WebSphere, and is there any indication from the information I've provided on what the issue could be? If more information is needed, please just let me know what you're looking for, and I'll try to find an answer. Thanks!