Do we have any oxtrust related logs available?

I have the logs available, indeed. Anyhow, I cannot see any option here to attach a file to the ticket. My colleagues around suggests me to ask you to add me into "The Economist" group, as I'm working for this company.

Meantime, here is the output of netstat showing listening ports; 8081 is there, 8082 is not: ``` root@xxxx:/opt/gluu/jetty/identity# netstat -nalt | grep -i listen tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8089 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:1636 0.0.0.0:* LISTEN tcp6 0 0 :::80 :::* LISTEN tcp6 0 0 127.0.0.1:8081 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN tcp6 0 0 :::8090 :::* LISTEN tcp6 0 0 :::443 :::* LISTEN ``` Similarly, only one Jetty process is listed: ``` root@xxxx:/opt/gluu/jetty/identity# ps -ef | grep -wv grep | grep java jetty 1614 1 2 12:49 ? 00:00:24 /opt/jre/bin/java -server -Xms256m -Xmx1676m -XX:+DisableExplicitGC -Dgluu.base=/etc/gluu -Dpython.home=/opt/jython -Dcatalina.base=/opt/gluu/jetty/oxauth -Djetty.logging.dir=/opt/gluu/jetty/oxauth/logs -Djetty.home=/opt/jetty -Djetty.base=/opt/gluu/jetty/oxauth -Djava.io.tmpdir=/opt/jetty-9.3/temp -jar /opt/jetty/start.jar jetty.http.host=localhost jetty.http.port=8081 jetty.state=/opt/gluu/jetty/oxauth/oxauth.state jetty-logging.xml jetty-started.xml start-log-file=/opt/gluu/jetty/oxauth/logs/start.log root@xxxx:/opt/gluu/jetty/identity# ```

Thanks Jozef. I am going to give a shot with my instance. Let's see how it goes.

If it helps, we are using a standard "Ubuntu 16.04" image on Amazon EC2 cloud.

Thanks much!

Jozef, Here are my findings: - Screenshot 'Jozef_only_OC_1604_status.png'. Status of base installation. - Screenshot 'Jozef_only_OC_1604_identity.png': This is second part of first screenshot. - Screenshot 'Jozef_with_Shib_OP.png': Status of Gluu Server with OpenID Connect + Shibboleth. Tried in DigitalOcean and my local VMWare. Both are same.

Another screenshot.

It seems that it works for you. The only notable difference in your setup I can see is that you have disabled "passport" component; it is enabled in my case. Cannot it clash with the "identity" module? I'm just guessing.

Ok, I'll check with passport bit as well.

Hi Jozef, Unfortunately couldn't reproduce your issue yet. Screenshot attached.

Hi Jozef, Maybe I can help, I've been thru the same problem as you (also on Ubuntu 16.04) and I figured out the script that runs identity is failing due to a missing JAVA_HOME environment variable. In order to fix that, issue this command ``` sudo service gluu-server-3.0.1 login ``` That will put you on the chroot environment. Once there, include the JAVA_HOME like this ``` vi /etc/environment ``` Add this line below the PATH line: > JAVA_HOME="/opt/jre" After that, you can either manually start identity or simply edit the chroot and restart gluu-server and its gonna work. Let me know if you have luck, coz I had some troubles right after that. Apache is running into an infinite redirect. Cheers,

We've opened an issue for this on Github: [https://github.com/GluuFederation/community-edition-setup/issues/274](https://github.com/GluuFederation/community-edition-setup/issues/274)

@William Lowe I'm not sure this is the same issue. The issue on Github says "gluu-server failed to start after restarting VM". The problem described here is about starting the identity component only, and it fails to start all the time, not just after a reboot. I've partially fix the problem with identity on port 8082 but now oxAuth is failing to start and bind to port 8081 I will keep posting if I find anything.

Guys, just to keep you up to date, I've uninstalled my gluu server and re-installed with the exact same modules as Jozef described. This time it worked. I had Asimba installed on the 1st time.

Thanks for your confirmation, Leni.