Hi, Luke. `./setup.py` cannot be re-run again to add some components. If you haven't installed one of them, the only **supported** way is to reinstall the whole thing. Please correct me if your issue is different from that.

So in that case can I export all my settings I spent all day configuring and just tell it to install Shibboleth as well?

We have export script like that, please check doc [here](https://www.gluu.org/docs/deployment/upgrading/). Let me check whether it's safe to use already (there were some issues before). I'll get back to you tomorrow, or you could try to run it anyway, just make sure you'll backup your current config.

So I guess it doesnt work on the current version? I have removed my ip addresses. [root@ community-edition-setup]# ./export24.py -bash: ./export24.py: Permission denied [root@ community-edition-setup]# chmod +x export24.py [root@ community-edition-setup]# ./export24.py Traceback (most recent call last): File "./export24.py", line 318, in <module> main() File "./export24.py", line 307, in main prepareLdapPW() File "./export24.py", line 289, in prepareLdapPW with open('/install/community-edition-setup/setup.properties.last', 'r') \ IOError: [Errno 2] No such file or directory: '/install/community-edition-setup/setup.properties.last' [root@ community-edition-setup]# ls export_24.log output setup_error.log static export24.py Properties.py setup.log templates genSchemaMarkdown.py Properties.pyc setup.properties.last tests ldif.py README.md setup.properties.sample update.sh LICENSE requirements.txt setup.py [root@ community-edition-setup]#

Luke, You need to run export script from _inside_ container. Feel free to check [this](https://gluu.org/docs/deployment/upgrading/) doc; though it's not your target but you will get export/import idea from here. One thing... if you didn't install Shibboleth bit in previous installation... using export / import script won't help you to restore your old data with new shib bit. [ Definitely there are options for hacking but personally I never tried ] Here is what I would do if I were in your case: - Do a new installation with Shibboleth in new VM. - Migrate old data **manually** from old vm to new vm.