By: Christopher Palmer user 31 Jan 2018 at 11:01 a.m. CST

2 Responses
Christopher Palmer gravatar

Hi there, We would like to introduce inbound SAML using Passport to our Gluu installation. Initially, we want to leverage Google as the IdP. It doesn't appear that Passport was installed during the initial setup, and it sounds like a reinstall is needed: https://support.gluu.org/installation/4688/installing-components-after-initial-gluu-install/

I was wondering if there was a way I can preserve my LDAP and configuration here. Our installation history is this: 3.0.2 -> 3.1.1 -> 3.1.2. If we can preserve it, do we essentially follow the 3.x -> 3.1.2 upgrade steps, basically leveraging the import and export scripts there? I realize we are on 3.1.x and the scripts may have been designed for 3.0.x, but perhaps there are no blocking differences?

Also, can you comment on using the Passport approach vs the single IDP SAML interception script? Does the latter need Asimba to be installed at setup time and what's the future/roadmap/support of this vs Passport?

I think it's a little unfortunate that some things require you to reinstall, but I get it. However, this could lead to administrators over-installing things upfront to avoid having to reinstall. Is the main issue here that more memory is needed and performance could suffer? If things are installed but NOT enabled, does that help?

Thanks!

By mohib zico staff 05 Feb 2018 at 1:09 a.m. CST

mohib zico gravatar

Hi Christopher,

I think you can try to use 'setup.properties.last' file. Take that file from old installation ( ~/install/community-edition-setup/ ); enable passport module in that configuration file; use that file in new installation.

I haven't tested that personally but it might work.

By Christopher Palmer user 06 Feb 2018 at 12:53 p.m. CST

Christopher Palmer gravatar

Thanks for the response, Mohib. I haven't tried it, but if I do, I can update this thread.