By: Sved Devs user 28 Jul 2020 at 5:09 p.m. CDT

11 Responses
Sved Devs gravatar
Followed guide at [SCIM Installation](https://gluu.org/docs/gluu-server/4.2/user-management/scim2/#installation) Expected: Install SCIM module and run it on port 8087. Actual: 1. The python script mentioned in the guide is not python3 compliant (all the print methods still use python2 syntax). E.g. ``` root@idp:/install/community-edition-setup# python3 post-setup-add-components.py -addscim File "post-setup-add-components.py", line 56 print "Current Gluu Version", gluu_version ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print("Current Gluu Version", gluu_version)? root@idp:/install/community-edition-setup# ``` 2. addscim flag is no longer supported. I get the message: ``` root@idp:/install/community-edition-setup# python3 post-setup-add-components.py -addscim usage: post-setup-add-components.py [-h] [-addshib] [-addpassport] [-addoxd] [-addcasa] [-addradius] post-setup-add-components.py: error: unrecognized arguments: -addscim root@idp ```

By Jose Gonzalez staff 29 Jul 2020 at 7:35 a.m. CDT

Jose Gonzalez gravatar
Hi Sved, That's really strange. The script is supposed to be this [one](https://github.com/GluuFederation/community-edition-setup/raw/version_4.2.0/post-setup-add-components.py) and I can see python3 `print` style as well as the `-addscim` there. Please download and copy the file inside chroot, assign execution permissions, and execute. Let us know the outcome.

By Sved Devs user 29 Jul 2020 at 8:13 a.m. CDT

Sved Devs gravatar
Hi Jose, Just tried it and here is the output. ``` root@idp:/install/community-edition-setup# python3 post-setup-add-components.py -addscim Current Gluu Version 4.2.0 Downloading Community Edition Setup 4.2.0 2020-07-29 13:12:39 URL:https://codeload.github.com/GluuFederation/community-edition-setup/zip/version_4.2.0 [643576] -> "/install/community-edition-setup/version_4.2.0.zip" [1] Extracting package Traceback (most recent call last): File "post-setup-add-components.py", line 88, in <module> from ces_current.setup import * File "/install/community-edition-setup/ces_current/setup.py", line 64, in <module> from pylib import gluu_utils ImportError: cannot import name 'gluu_utils' root@idp:/install/community-edition-setup# ``` For completeness I also made the script executable and ran it with the same result.

By Sved Devs user 29 Jul 2020 at 8:56 a.m. CDT

Sved Devs gravatar
Are there any Python environment variables I need to setup to get this working?

By Jose Gonzalez staff 29 Jul 2020 at 9:12 a.m. CDT

Jose Gonzalez gravatar
No, this should work out of the box. Sounds like scripts in `/install/community-edition-setup` have problems in your environment. I remember there was a problem with 4.2 packaging and for a brief period of time we had defective packages in the repository. This might be the cause. May I know when you did your installation (ie package was downloaded)?

By Sved Devs user 29 Jul 2020 at 11:34 a.m. CDT

Sved Devs gravatar
June 30.

By Michael Schwartz staff 29 Jul 2020 at 12:55 p.m. CDT

Michael Schwartz gravatar
That's before the release date for 4.2....

By Jose Gonzalez staff 29 Jul 2020 at 1:45 p.m. CDT

Jose Gonzalez gravatar
Yes, 4.2 was released by Jul14th so you are probably using a beta testing package. I highly recommend to do a fresh install and apply your configs again. Trying to import data from a beta install might bring you even more trouble.

By Sved Devs user 29 Jul 2020 at 2:19 p.m. CDT

Sved Devs gravatar
Sorry, my bad. I installed 4.1 on June/30, but upgraded it to 4.2 on Jul 19th (using the upgrade script from https://raw.githubusercontent.com/GluuFederation/community-edition-package/master/update/4.2.0/upg4xto420.py). Would you still suggest I reinstall?

By Michael Schwartz staff 29 Jul 2020 at 2:23 p.m. CDT

Michael Schwartz gravatar
If you don't have a ton of config, re-install is cleaner.

By Sved Devs user 30 Jul 2020 at 6:46 p.m. CDT

Sved Devs gravatar
Did it (and installed SCIM during the initial setup itself). Just wish there was some script one could use to copy settings/clients/users over to the new system. They were not so many that I request you for alternate paths, and not so few that I could just rebuild them in a short time. But, as always, thank you so much for the support.

By Jose Gonzalez staff 31 Jul 2020 at 9:47 a.m. CDT

Jose Gonzalez gravatar
> Just wish there was some script one could use to copy settings/clients/users over to the new system I understand, however, this creates a new script to maintain for every release. Problem here was that post-setup script has issues on upgraded instances. We are working on that currently.