OpenIDM installation

[rzyb]

Linux install info: https://doc.openidentityplatform.org/openidm/install-guide/chap-install
Download at: https://github.com/OpenIdentityPlatform/OpenIDM/releases
cd /opt && mkdir openIDM
wget https://github.com/OpenIdentityPlatform/OpenIDM/archive/refs/tags/7.0.2.tar.gz -or-
wget https://github.com/OpenIdentityPlatform/OpenIDM/releases/download/7.0.2/openidm-7.0.2.zip
openIDM Install:
tar -zxvf 7.0.2.tar.gz or unzip openidm-7.0.2.zip
cd /path/to/OpenIDM-7.0.2/openidm/ && ./getting-started.sh > No SLF4J providers were found.->
dnf list SLF4J
Installed Packages
slf4j.noarch 1.7.30-16.el9

• stopping point
  Next approach:
  vi /path/to/OpenIDM-7.0.2/openidm/conf/boot/boot.properties > set port 8081 since tomcat is using 8080
  cd /path/to/OpenIDM-7.0.2/openidm/bin/ && ./startup.sh
  Executing ./startup.sh...
  Using OPENIDM_HOME: /apps/openIDM/OpenIDM-7.0.2/openidm
  Using PROJECT_HOME: /apps/openIDM/OpenIDM-7.0.2/openidm
  Using OPENIDM_OPTS: -Dlogback.configurationFile=conf/logging-config.groovy
  Using LOGGING_CONFIG: -Djava.util.logging.config.file=/apps/openIDM/OpenIDM-7.0.2/openidm/conf/logging.properties
  WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
  WARNING: sun.misc.Unsafe::staticFieldOffset has been called by org.apache.felix.framework.util.SecureAction (file:/apps/openIDM/OpenIDM-7.0.2/openidm/bin/felix.jar)
  WARNING: Please consider reporting this to the maintainers of class org.apache.felix.framework.util.SecureAction
  WARNING: sun.misc.Unsafe::staticFieldOffset will be removed in a future release
  Using boot properties at /apps/openIDM/OpenIDM-7.0.2/openidm/conf/boot/boot.properties
  SLF4J(W): No SLF4J providers were found.
  SLF4J(W): Defaulting to no-operation (NOP) logger implementation
  SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details.
  -> OpenIDM ready
  OpenIDM version "7.0.2" (revision: 12374) 2026-02-05T08:07:06Z UNKNOWN

->
https://localhost:8443/system/console = not accessible
lynx https://localhost:8443/system/console = not accessible
lynx https://localhost:8443/openidm/security = not accessible
Cannot proceed any further. Can someone help with this please?

[vharseko]

Getting-Started

Wait for the message OpenIDM ready and go:

User self service UI: http://localhost:8080/ (openidm-admin/openidm-admin)
Admin UI: http://localhost:8080/admin/ (openidm-admin/openidm-admin)
Apache Felix UI: http://localhost:8080/system/console/ (admin/admin)

[rzyb]

Thanks for the Admin UI and Self Service UI links however I am unable to get to them. I can only get to the Apache Felix UI system console. Any thoughts/help would be greatly appreciated!!

[vharseko]

try docker

docker run -h idm-01.domain.com -p 8080:8080 -p 8443:8443 --name idm-01 openidentityplatform/openidm

[rzyb]

Greetings, I meant to respond earlier but got carried away with other things. The container works nicely to demonstrate its functions; however, we need to integrate Workday & Banner ERPs, Postgresql DB, and Active Directory systems with the VM version. I followed the docs for the setup installation but cannot get the VM version of the app to work. Can you assist or perhaps point me to someone who can help please? Thank you!

…

On Thu, Jun 4, 2026 at 12:39 AM Valery Kharseko ***@***.***> wrote: try docker docker run -h idm-01.domain.com -p 8080:8080 -p 8443:8443 --name idm-01 openidentityplatform/openidm — Reply to this email directly, view it on GitHub <https://urldefense.com/v3/__https://github.com/OpenIdentityPlatform/OpenIDM/discussions/182?email_source=notifications&email_token=ALZ4NNO3T6XU34HBHC3U6YT46ERRZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZRG43DSNJZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW*discussioncomment-17176959__;Iw!!Ka_JY85zDv0FFw!nW-jiq7X2JLCmTVC9afOuzRpG4ke-2aGkp_ttbjDFwvjEWk32kO0j8-iPiN7jYuMsNGpQdRHw8CmepDOW6GrjtTBLUE3Ew$>, or unsubscribe <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ALZ4NNNVEEVDSE5W4FVDDKT46ERRZAVCNFSM6AAAAACZZNRALWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMJXGY4TKOI__;!!Ka_JY85zDv0FFw!nW-jiq7X2JLCmTVC9afOuzRpG4ke-2aGkp_ttbjDFwvjEWk32kO0j8-iPiN7jYuMsNGpQdRHw8CmepDOW6GrjtS_fNB4rg$> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://urldefense.com/v3/__https://github.com/notifications/mobile/ios/ALZ4NNJYNXRTP52SZARJDI346ERRZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZRG43DSNJZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM__;!!Ka_JY85zDv0FFw!nW-jiq7X2JLCmTVC9afOuzRpG4ke-2aGkp_ttbjDFwvjEWk32kO0j8-iPiN7jYuMsNGpQdRHw8CmepDOW6GrjtQabJHdfQ$> and Android <https://urldefense.com/v3/__https://github.com/notifications/mobile/android/ALZ4NNPG6LQP2QCILN3EG6346ERRZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZRG43DSNJZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE__;!!Ka_JY85zDv0FFw!nW-jiq7X2JLCmTVC9afOuzRpG4ke-2aGkp_ttbjDFwvjEWk32kO0j8-iPiN7jYuMsNGpQdRHw8CmepDOW6GrjtSk9MlVtA$>. Download it today! You are receiving this because you authored the thread.Message ID: <OpenIdentityPlatform/OpenIDM/repo-discussions/182/comments/17176959@ github.com>

[vharseko]

Please check https://github.com/OpenIdentityPlatform/OpenIDM/blob/master/Dockerfile

[vharseko]

Hi @rzyb 👋

Good news: OpenIDM actually started successfully. Your log shows -> OpenIDM ready and the version banner right after the SLF4J lines, so the server is up. The issue is just how you're trying to reach the UI.

1. The SLF4J messages are harmless warnings, not errors

SLF4J(W): is a Warning. Those lines come from the outer Java launcher process before OSGi starts; OpenIDM's own logging runs through logback/JUL (-Dlogback.configurationFile=conf/logging-config.groovy and conf/logging.properties). Installing the OS package (dnf install slf4j) does nothing for OpenIDM — it ships its own libraries inside bundle/. The sun.misc.Unsafe / Felix warnings are also harmless on newer JDKs.

2. You're hitting the wrong URLs

• /system/console is the OSGi/Felix console (a dev/debug tool with its own separate admin:admin auth — it's even recommended to remove it in production). It is not the admin entry point.
• /openidm/security is part of the REST API, not a UI page, so it won't render in a browser.

The correct addresses are:

Purpose	URL
Admin UI	https://localhost:8443/admin
Self-Service UI	https://localhost:8443/
Credentials	openidm-admin / openidm-admin

3. lynx will not work

The Admin and Self-Service UIs are full JavaScript applications. lynx is a text browser with no JS support, so it can never render them. Use a normal browser (Firefox/Chrome) and accept the self-signed-certificate warning on first access.

4. Mind your changed port

You set openidm.port.http=8081, but openidm.port.https is still 8443. So:

• HTTPS → https://localhost:8443/admin
• HTTP → http://localhost:8081/admin (not 8080)

Steps to confirm everything works

# 1. Verify the server is listening
ss -ltnp | grep -E '8443|8081'

# 2. Hit the REST API with curl (not lynx)
curl -k -u openidm-admin:openidm-admin https://localhost:8443/openidm/info/ping
curl -k -u openidm-admin:openidm-admin http://localhost:8081/openidm/info/ping

# 3. Open in a real browser
#    https://localhost:8443/admin   (login: openidm-admin / openidm-admin)
#    http://localhost:8081/admin   (login: openidm-admin / openidm-admin)

If you're connecting from a different machine than the server (/apps/openIDM/...), replace localhost with the server's IP/hostname and open the ports in the firewall:

firewall-cmd --add-port=8443/tcp --permanent
firewall-cmd --add-port=8081/tcp --permanent
firewall-cmd --reload

(The Getting Started guide explicitly lists opening the HTTP/HTTPS ports as a prerequisite.)

Let us know how curl .../info/ping responds — that will immediately tell us whether the server is reachable.

[rzyb]

Awesome response and with much appreciation and gratitude! Thank you so much for the feedback! I will go through this on Monday! Hope you have a great weekend!

…

On Thu, Jun 11, 2026 at 1:20 AM Valery Kharseko ***@***.***> wrote: Hi @rzyb <https://urldefense.com/v3/__https://github.com/rzyb__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGULjnDUZnQ$> 👋 Good news: *OpenIDM actually started successfully.* Your log shows -> OpenIDM ready and the version banner right after the SLF4J lines, so the server is up. The issue is just *how* you're trying to reach the UI. 1. The SLF4J messages are harmless warnings, not errors SLF4J(W): is a *W*arning. Those lines come from the outer Java launcher process before OSGi starts; OpenIDM's own logging runs through logback/JUL ( -Dlogback.configurationFile=conf/logging-config.groovy and conf/logging.properties). Installing the OS package (dnf install slf4j) does nothing for OpenIDM — it ships its own libraries inside bundle/. The sun.misc.Unsafe / Felix warnings are also harmless on newer JDKs. 2. You're hitting the wrong URLs - /system/console is the *OSGi/Felix console* (a dev/debug tool with its own separate admin:admin auth — it's even recommended to remove it in production). It is *not* the admin entry point. - /openidm/security is part of the *REST API*, not a UI page, so it won't render in a browser. The correct addresses are: Purpose URL Admin UI https://localhost:8443/admin <https://urldefense.com/v3/__https://localhost:8443/admin__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUJFklzdYw$> Self-Service UI https://localhost:8443/ <https://urldefense.com/v3/__https://localhost:8443/__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUIER00Sow$> Credentials openidm-admin / openidm-admin 3. lynx will not work The Admin and Self-Service UIs are full JavaScript applications. lynx is a text browser with no JS support, so it can never render them. Use a normal browser (Firefox/Chrome) and accept the self-signed-certificate warning on first access. 4. Mind your changed port You set openidm.port.http=8081, but openidm.port.https is still 8443. So: - HTTPS → https://localhost:8443/admin <https://urldefense.com/v3/__https://localhost:8443/admin__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUJFklzdYw$> - HTTP → http://localhost:8081/admin <https://urldefense.com/v3/__http://localhost:8081/admin__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUJ-OX0ZWA$> (not 8080) Steps to confirm everything works # 1. Verify the server is listening ss -ltnp | grep -E '8443|8081' # 2. Hit the REST API with curl (not lynx) curl -k -u openidm-admin:openidm-admin https://localhost:8443/openidm/info/ping <https://urldefense.com/v3/__https://localhost:8443/openidm/info/ping__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUJGe8lTEQ$> curl -k -u openidm-admin:openidm-admin http://localhost:8081/openidm/info/ping <https://urldefense.com/v3/__http://localhost:8081/openidm/info/ping__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUJBFHZpNg$> # 3. Open in a real browser# https://localhost:8443/admin <https://urldefense.com/v3/__https://localhost:8443/admin__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUJFklzdYw$> (login: openidm-admin / openidm-admin)# http://localhost:8081/admin <https://urldefense.com/v3/__http://localhost:8081/admin__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUJ-OX0ZWA$> (login: openidm-admin / openidm-admin) If you're connecting from a different machine than the server ( /apps/openIDM/...), replace localhost with the server's IP/hostname and open the ports in the firewall: firewall-cmd --add-port=8443/tcp --permanent firewall-cmd --add-port=8081/tcp --permanent firewall-cmd --reload (The Getting Started guide explicitly lists opening the HTTP/HTTPS ports as a prerequisite.) Let us know how curl .../info/ping responds — that will immediately tell us whether the server is reachable. — Reply to this email directly, view it on GitHub <https://urldefense.com/v3/__https://github.com/OpenIdentityPlatform/OpenIDM/discussions/182?email_source=notifications&email_token=ALZ4NNOJFEODYTK4UTV73DD47JTU7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGYYDSMZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y*discussioncomment-17260939__;Iw!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUK-m6l1Dw$>, or unsubscribe <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ALZ4NNKGMC3YKBQ45E3WXFT47JTU7AVCNFSNUABIKJSXA33TNF2G64TZHMYTENRQHA2TSMZRHNCGS43DOVZXG2LPNY5TCMBQG42DSNJWUF3AE__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUId-8nF7Q$> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://urldefense.com/v3/__https://github.com/notifications/mobile/ios/ALZ4NNPVTMDOPHSFB67AY7347JTU7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGYYDSMZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUIYy5awLg$> and Android <https://urldefense.com/v3/__https://github.com/notifications/mobile/android/ALZ4NNJXGGDNZLT3HIOSZYL47JTU7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGYYDSMZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ__;!!Ka_JY85zDv0FFw!h9M8vGv0edwoesdsT_6YHUE6rfVxACMgYk6k4m5AP4pLeXyA5-r6t4ohoZ3oPFglbrF7XnM5a1BBqhhMABNQGUKxK0KUEQ$>. Download it today! You are receiving this because you were mentioned.Message ID: <OpenIdentityPlatform/OpenIDM/repo-discussions/182/comments/17260939@ github.com>