Gluu Casa for 3.1.7

By: Kevin Fletcher named 18 Mar 2020 at 2:35 p.m. CDT

31 Responses
Kevin Fletcher gravatar
I would like to know if there are any plans to offer Gluu Casa for Gluu version 3.1.7. We have need to use 3.1.7 in production but we also need to have Gluu Casa and it currently is offered for 3.1.6. We performed an upgrade of one of our servers from 3.1.6 to 3.1.7 and noticed that it broke Gluu Casa that we had installed.
CentOS 7.6
closed

Answers

By Mohib Zico Account Admin 19 Mar 2020 at 4:03 a.m. CDT

Copy
Mohib Zico gravatar
Please allow me to talk internally a bit.

By Mohib Zico Account Admin 19 Mar 2020 at 8:12 a.m. CDT

Copy
Mohib Zico gravatar
Kevin, Do you need it for CentOS7.x? Seems like we already has one for Ubuntu 16.

By Kevin Fletcher named 19 Mar 2020 at 8:15 a.m. CDT

Copy
Kevin Fletcher gravatar
Yes, we are currently using Centos 7.x on all of our Gluu instances. We are not ready to migrate to Gluu 4.x just yet as it will require rework of our applicaitons which is why Gluu 3.1.7 running with Gluu Casa would be very nice as it solves issues that we have been facing.

By Mohib Zico Account Admin 20 Mar 2020 at 2:49 a.m. CDT

Copy
Mohib Zico gravatar
Got it, I am requesting packaging team to prpeare Casa for CentOS7.x

By Mohib Zico Account Admin 20 Mar 2020 at 7:39 a.m. CDT

Copy
Mohib Zico gravatar
Here is the package: https://repo.gluu.org/centos/7-testing/gluu-casa-3.1.7-1.centos7.noarch.rpm

By Kevin Fletcher named 20 Mar 2020 at 4:20 p.m. CDT

Copy
Kevin Fletcher gravatar
Question, we were running 3.1.6.sp1 of Gluu and performed an upgrade inside the chroot to 3.1.7 via the shell script. The problem now is that it broke Gluu Casa 3.1.6. When I try to upgrade Gluu Casa to 3.1.7 outside the chroot environment it wants to upgrade Gluu server rpm to 3.1.7. What is the proper way to accomplish this?
2020-03-20_161228.png

By Mohib Zico Account Admin 21 Mar 2020 at 12:13 a.m. CDT

Copy
Mohib Zico gravatar
>> we were running 3.1.6.sp1 of Gluu and performed an upgrade inside the chroot to 3.1.7 via the shell script. Sorry, how did you upgrade Gluu Server again?

By Kevin Fletcher named 21 Mar 2020 at 4:29 p.m. CDT

Copy
Kevin Fletcher gravatar
Upgrade from 3.1.x to 3.1.6.sp1# To perform an in-place upgrade from Gluu Server 3.1.x to 3.1.6.sp1, download and run our in-place upgrade script, following these instructions: https://gluu.org/docs/ce/3.1.6/upgrade/ Log in to your server with service gluu-server-3.1.6 login Download the upgrade script with wget https://repo.gluu.org/upd/3-1-6-sp1-upg.sh Run the script with sh 3-1-6-sp1-upg.sh When the script has finished, restart your server: logout service gluu-server-3.1.6 restart

By Mohib Zico Account Admin 22 Mar 2020 at 3:21 a.m. CDT

Copy
Mohib Zico gravatar
Got it, thanks. Regarding, CASA... I have to check if 'upgrade' is possible or not. I'll talk to associated Dev.

By Kevin Fletcher named 24 Mar 2020 at 8:53 a.m. CDT

Copy
Kevin Fletcher gravatar
Any updates on this?

By Mohib Zico Account Admin 24 Mar 2020 at 9:25 a.m. CDT

Copy
Mohib Zico gravatar
Yes... Dev said.. there shouldn't be any issue in CASA upon upgrade. Because... CASA 3.1.7 is actually 3.1.6 codebase. Can you please share what type of error you are getting when it's broken? Also.. I"ll try to test it by myself.

By Kevin Fletcher named 27 Mar 2020 at 11:01 a.m. CDT

Copy
Kevin Fletcher gravatar
The error that I am getting when I try to navigate to the Gluu Casa web page is: An error occurred Gluu Casa did not start properly. Contact your admin. When I try to install the https://repo.gluu.org/centos/7-testing/gluu-casa-3.1.7-1.centos7.noarch.rpm it will prompt me to install the gluu-server-3.1.7 server dependency. If I go ahead with the install I will end up with 2 different folders in /opt: /opt/gluu-server-3.1.6/ (Which is the 3.1.6.sp1 that was upgraded to 3.1.7) and /opt/gluu-server-3.1.7/ (Which is the 3.1.7 install via the dependency) That is why I was asking what the preferred method was to upgrade. If I follow the upgrade process via the Gluu docs for Gluu server, it tells me to log into the chroot environment to perform the upgrade via the shell script. When I do that it only updates the files and not the RPM outside the chroot environment. When I try to install the upgrade for Gluu Casa outside the chroot environment it will see that I have Gluu 3.1.6 installed and then will try to install the 3.1.7 rpm.

By Mohib Zico Account Admin 27 Mar 2020 at 11:43 a.m. CDT

Copy
Mohib Zico gravatar
Yes, kind of looping problem. I asked our CASA developer to take a look. I'll also test as soon as I can manage some time.

By Kevin Fletcher named 02 Apr 2020 at 8:35 a.m. CDT

Copy
Kevin Fletcher gravatar
Can I get an update on this? Any progress?

By Mohib Zico Account Admin 02 Apr 2020 at 8:38 a.m. CDT

Copy
Mohib Zico gravatar
Sorry Kevin, I haven't been able to test it. This is added in my high priority list. I'll test it ASAP.

By Mohib Zico Account Admin 02 Apr 2020 at 4:03 p.m. CDT

Copy
Mohib Zico gravatar
**Status** I have a 3.1.6 with CASA 3.1.6 ready. Will perform upgrade tomorrow. Action items will be: - I will perform Gluu Server upgrade by [this](https://www.gluu.org/docs/gluu-server/3.1.7/upgrade/#upgrade-from-31x-to-317) and will see how CASA does. - If CASA breaks.. will try to install / upgrade 3.1.7 CASA separately.

By Mohib Zico Account Admin 03 Apr 2020 at 2:51 p.m. CDT

Copy
Mohib Zico gravatar
Kevin, I preformed upgrade ( only Gluu Server upgrade, not CASA ) and getting attached situation now. Are you also getting same?
Capture.PNG

By Kevin Fletcher named 03 Apr 2020 at 7:04 p.m. CDT

Copy
Kevin Fletcher gravatar
Yes, that is the error message that I was getting.

By Mohib Zico Account Admin 04 Apr 2020 at 8:42 a.m. CDT

Copy
Mohib Zico gravatar
Ok, thanks for confirmation. Seems like it's oxd-server issue. After upgrade for some reason CASA can't read oxd-server config and failing. Error from casa.log: ``` 3-04 20:09:31.733 INFO [main] gluu.casa.core.ZKService ZKService.java:57- ZK initialized 03-04 20:09:31.960 INFO [main] gluu.casa.core.ConfigurationHandler ConfigurationHandler.java:84- ConfigurationHandler inited 03-04 20:09:32.214 INFO [main] gluu.casa.conf.MainSettingsProducer MainSettingsProducer.java:60- init. Obtaining global settings 03-04 20:09:32.217 INFO [main] gluu.casa.conf.MainSettingsProducer MainSettingsProducer.java:63- init. Gluu base inferred was /etc/gluu 03-04 20:09:32.440 INFO [main] gluu.casa.core.LogService LogService.java:97- Using INFO for log level 03-04 20:09:33.202 INFO [main] gluu.casa.core.LdapService LdapService.java:359- Backend ldap for cache refresh was not detected 03-04 20:09:33.202 INFO [main] gluu.casa.core.LdapService LdapService.java:95- LDAPService was initialized successfully 03-04 20:09:33.209 INFO [main] gluu.casa.core.ZKService ZKService.java:92- Loading application labels 03-04 20:09:33.210 INFO [main] gluu.casa.core.ZKService ZKService.java:117- War resource bundles are: [general, admin, user] 03-04 20:09:33.213 INFO [main] gluu.casa.core.ZKService ZKService.java:151- Labels registered 03-04 20:09:33.226 INFO [main] gluu.casa.misc.CssRulesResolver CssRulesResolver.java:35- CssRules ZK VariableResolver initialized successfully 03-04 20:09:33.639 INFO [main] casa.core.filter.CorsFilter CorsFilter.java:39- CORS filter initialized 03-04 20:09:38.324 INFO [casaScheduler_Worker-1] gluu.casa.core.ConfigurationHandler ConfigurationHandler.java:256- Using default value of 2 for minimum number of credentials to enable strong authentication 03-04 20:09:38.446 ERROR [casaScheduler_Worker-1] gluu.casa.core.OxdService OxdService.java:105- The following must be present in configuration file: host, port, redirect URI, post logout URI, and front channel logout URI 03-04 20:09:38.446 WARN [casaScheduler_Worker-1] gluu.casa.core.ConfigurationHandler ConfigurationHandler.java:167- oxd configuration could not be initialized. 03-04 20:09:38.447 ERROR [casaScheduler_Worker-1] gluu.casa.core.ConfigurationHandler ConfigurationHandler.java:239- Application not in operable state, please fix configuration issues before proceeding. 03-04 20:09:38.447 INFO [casaScheduler_Worker-1] gluu.casa.core.ConfigurationHandler ConfigurationHandler.java:240- === WEBAPP INITIALIZATION FAILED === ``` We are trying to figure that issue now.

By Mohib Zico Account Admin 06 Apr 2020 at 12:48 p.m. CDT

Copy
Mohib Zico gravatar
I think there is some issue with Casa in 3.1.7. I couldn't install it either. Asked @Jose.Gonzalez and rest of the CASA team to test this rpm in Gluu 3.1.7.

By Kevin Fletcher named 06 Apr 2020 at 3:07 p.m. CDT

Copy
Kevin Fletcher gravatar
Thank you for the update. Keep me posted.

By Kevin Fletcher named 09 Apr 2020 at 8:17 a.m. CDT

Copy
Kevin Fletcher gravatar
Any updates on this?

By Mohib Zico Account Admin 09 Apr 2020 at 8:25 a.m. CDT

Copy
Mohib Zico gravatar
Yes... there was some issue with 3.1.7 base code which prohibited CASA 3.1.7 to install properly. Now, if you install fresh 3.1.7 and then install CASA.. it works okay.

By Mohib Zico Account Admin 15 Apr 2020 at 10:15 a.m. CDT

Copy
Mohib Zico gravatar
Hello Kevin, Just touching base to know if you are waiting on us for something here in this ticket. Thanks!

By Kevin Fletcher named 15 Apr 2020 at 10:32 a.m. CDT

Copy
Kevin Fletcher gravatar
In response to your message on 4/9/20, can I just run another upgrade to 3.1.7 on top of 3.1.7? Installing 3.1.7 all over from the beginning is not really an option as the system is being used currently. Please advise.

By Mohib Zico Account Admin 15 Apr 2020 at 10:35 a.m. CDT

Copy
Mohib Zico gravatar
Gotcha... "upgrade". Okay.. I'll test it then. 3.1.6 to 3.1.7 upgrade, right?

By Kevin Fletcher named 15 Apr 2020 at 4:32 p.m. CDT

Copy
Kevin Fletcher gravatar
Yes.

By Mohib Zico Account Admin 20 Apr 2020 at 9:38 a.m. CDT

Copy
Mohib Zico gravatar
Hi Kevin, Seems like we need Developer to look into it. I created a github issue on this: https://github.com/GluuFederation/casa/issues/119

By Mohib Zico Account Admin 23 Apr 2020 at 2:10 p.m. CDT

Copy
Mohib Zico gravatar
Hello Kevin, We figured what actually breaking CASA after upgrade. It's 'casa.json' file. After upgrade, the `casa.json` file lost some configuration attributes which are essential to connect with oxd-server. I have prepared a screencast of this troubleshooting for you. Where: - I just upgraded a 3.1.6 to 3.1.7 and restarting Gluu-Server container. - Tested 3.1.7 oxTrust login after upgrade. - Tested 3.1.7 CASA login after upgrade, which is failing. - Modifying "casa.json" file, adding some host/port for oxd-server - Keeping 'client' configuration snippet blank so CASA can register 'new client'. You can also use old client config if you have backup from 3.1.6. ( The way I have in sublime text ). - Restarted CASA service. - Tested CASA again. - A new CASA cient is registered and you will see consent page. Here is the screencast: https://youtu.be/YCUUEiSko1E Let me know if you have any question or confusion please.

By Kevin Fletcher named 28 Apr 2020 at 11:24 a.m. CDT

Copy
Kevin Fletcher gravatar
Sorry for the delay. I was trying to get confirmation that this is resolved. The fix you described in the video worked. I am closing the call now.

By Mohib Zico Account Admin 28 Apr 2020 at 11:41 a.m. CDT

Copy
Mohib Zico gravatar
Great! Thanks for confirmation. No problem at all.

Post an answer