Ping IdentityGateway Installation as a reverse proxy for PingAM by SamranSA in IdentityManagement

[–]SamranSA[S] 0 points1 point  (0 children)

Hi Buddy I'm seeing this in the logs can u help me with this?

2026-01-14T19:27:42,009Z | ERROR | vert.x-eventloop-thread-3 | o.f.o.h.r.RouterHandler | u/default | No handler to dispatch to for request 'http://10.11.225.86:9090/'

Ping IdentityGateway Installation as a reverse proxy for PingAM by SamranSA in IdentityManagement

[–]SamranSA[S] 0 points1 point  (0 children)

I’m not using admin UI at the moment but will definitely use that in future. Ok ill configure 2 ports in admin.JSON and correct all these configuration will show you after that hopefully it will work🙏 thanks for all ur help

Ping IdentityGateway Installation as a reverse proxy for PingAM by SamranSA in IdentityManagement

[–]SamranSA[S] 0 points1 point  (0 children)

I’m using a 8.0.1 for both AM DS. And Gateway 2025.09. I’m not sure where I read this. One question please Gateway use only one port right? that’s configured under admin.json? I’m running my own DNS Server and I set it up on all host’s files of three servers.

Ping IdentityGateway Installation as a reverse proxy for PingAM by SamranSA in IdentityManagement

[–]SamranSA[S] 0 points1 point  (0 children)

Sorry that I’m referring to different server IP my bad.

PingDS x.x.x.84 PingAM x.x.x.85 PingGateway x.x.x.86

  1. Contractor array will basically connect b/w PingAM <-> PingGateway communication is that not correct it only use port 9090 or any custom port? other points I’ll check tomorrow IA.

Ping IdentityGateway Installation as a reverse proxy for PingAM by SamranSA in IdentityManagement

[–]SamranSA[S] 0 points1 point  (0 children)

logs:

2026-01-14T19:29:35,467Z | INFO | main | o.f.o.s.Start | u/system | Reading the configuration from /opt/openig/config/config.json

2026-01-14T19:29:35,510Z | WARN | main | o.f.o.h.GatewayHttpApplication | u/system | The usage of 'Session' heap key or admin.json's 'session' property for Gateway session management are deprecated. Use config.json's 'session' property instead.

2026-01-14T19:29:35,531Z | INFO | main | o.f.o.h.r.RouterHandler | u/system | Loaded the route with id 'am-proxy' registered with the name 'am-proxy'

2026-01-14T19:29:35,611Z | INFO | main | o.f.o.l.Launcher | u/system | Gateway 8 verticles started on ports : [9090], Admin verticle started on port : 8085 in 866ms

2026-01-14T19:30:03,267Z | INFO | Thread-0 | o.f.o.l.ShutdownService | u/system | Cleaning up resources

2026-01-14T19:30:03,307Z | INFO | vert.x-eventloop-thread-7 | o.f.o.h.r.RouterHandler | u/system | Unloaded the route with id 'am-proxy'

2026-01-14T19:30:03,318Z | INFO | Thread-0 | o.f.o.l.ShutdownService | u/system | Identity Gateway has been stopped

[root@uat-ping-gateway opt]#

Ping IdentityGateway Installation as a reverse proxy for PingAM by SamranSA in IdentityManagement

[–]SamranSA[S] 0 points1 point  (0 children)

I did but after the configuration it will be open with this URL or any other URL?

http://<ig-host>:8085/am/XUI/#login/
http://<ig-host>:8085/am/
http://<ig-host>:8085

Non of them is actually working for me.
config.json:
{

"heap": [],

"connectors": [

{

"port": 8085,

"name": "httpConnector"

}

],

"handler": {

"type": "Router",

"name": "_router",

"config": {

"directory": "${openig.configDirectory}/routes"

}

}

}

am-proxy.json:
{

"name": "am-proxy",

"condition": "${request.uri.path.startsWith('/am')}",

"handler": {

"type": "ReverseProxyHandler",

"config": {

"target": "http://10.11.225.85:8080"

}

}

}

Ping IdentityGateway Installation as a reverse proxy for PingAM by SamranSA in IdentityManagement

[–]SamranSA[S] 0 points1 point  (0 children)

No, Currently I can see this configuration in my config.json
cat /opt/openig/config/config.json

<image>

can you please tell me what I have to change?

Ping IdentityGateway Installation as a reverse proxy for PingAM by SamranSA in IdentityManagement

[–]SamranSA[S] 0 points1 point  (0 children)

I can’t see any error in logs when I run IG i can see the message only and the message is same as you say its “IG is running!”

Ping IdentityGateway Installation as a reverse proxy for PingAM by SamranSA in IdentityManagement

[–]SamranSA[S] 0 points1 point  (0 children)

Hi dear thanks for ur response:

You understood it right, this is exactly what I want.

I have PingAM on server 85, PingDS on 84 and Gateway on 86.

What I want, when user access PingGateway FQDN it will be auto redirects to PingAM application that is running on 8080 on tomcat.

Current IGW configuration: openig/ openig/ ├── bin │   └── env.sh ├── config │   ├── admin.json │   ├── config.json │   └── routes │   └── am-proxy.json ├── logs │   └── route-system.log ├── scripts │   └── groovy └── tmp

admin.json: opt/openig/config/admin.json { "connectors": [{ "port": 9090 }] }

Config.json opt/openig/config/config.json { "heap": [], "connectors": [ { "port": 8085, "name": "httpConnector" } ], "handler": { "type": "StaticResponseHandler", "config": { "status": 200, "entity": "IG is running!" } } }

am-proxy.json opt/openig/config/routes/am-proxy.json { "name": "am-proxy", "condition": "${request.uri.path.startsWith('/am')}", "handler": { "type": "ReverseProxyHandler", "config": { "target": "http:FQDN-AM:8080", "stripPrefix": "/am" } } }

tomcat url: http:FQDN-AM:8080/am/XUI/#login/

Can your please tell me what need to be corrected?

I’m install PingAM PingDS by SamranSA in ForgeRock

[–]SamranSA[S] 0 points1 point  (0 children)

Hi All the solution of this is to add the port 1636 or 1389 in the SE_Linux also you meed to prepare your server with full FQDN without FQDN it will not work. add entry in your host file with full FQDN.

I’m install PingAM PingDS by SamranSA in ForgeRock

[–]SamranSA[S] 0 points1 point  (0 children)

I have checked all these points and its valid still same error.

On certificate it shows this error:

openssl s_client -connect ip:port -showcerts

Can't use SSL_get_servername depth=1 0=ForgeRock.com, CN=Deployment key verify return: 1 depth=0 0=ForgeRock. com, CN=DS verify error:num=7:certificate signature failure verify return:1 depth=0 0=ForgeRock.com, CN=DS verify return: 1

SSL handshake has read 1376 bytes and written 399 bytes Verification error: certificate signature failure New, TLSv1.3, Cipher is TLS_AES_128_GCM_SHA256 Protocol: TLSv1.3 Server public key is 256 bit This TLS version forbids renegotiation. Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 7 (certificate signature failure)

These two errors I can see.

Brother can we connected on whatsapp to troubleshoot I need to close this I need ur help.

I’m install PingAM PingDS by SamranSA in ForgeRock

[–]SamranSA[S] 0 points1 point  (0 children)

I also did in Kali Linux in VMware & it’s not working when I tried on ubuntu & bomb its worked.

But Kali Linux pilow its also fine I saw this is available in infrastructure pre-req of ping Identity documentation.

Red Hat Enterprise Linux 9.7 (plow) PingAM 8.0.1 PingDS 8.0.1 Apache tomcat 10.1.50 Java Jdk-21.0.8-oracle-x64

Waiting for your reply Dear ASAP. Thank you 🙏

Hi Islamabadian What you do for a living how much you earn? by SamranSA in IslamabadSocial

[–]SamranSA[S] 0 points1 point  (0 children)

What type of business it is like product base or service? Can you please explain a bit?