You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to enable deployment and testing of inventory CKAN in non-BSP environments, we want the setup of local vs SAML authentication to be configurable with a variable.
Acceptance Criteria
GIVEN sandbox environments are configured with inventory_ckan_saml2_enabled: false
WHEN the inventory.yml playbook is run
THEN the environment is configured with CKAN's native user/password login
GIVEN that the BSP environments are configured with inventory_ckan_saml2_enabled: true
WHEN the inventory.yml playbook is run
THEN the environment is configured with SAML2 authentication
Was just chatting with @jbrown-xentity@pjsharpe07, we probably don't want to do this work, at least not as described. We can pull in a few similar changes from 1c86878 and 71b64e9, but we don't actually need to combine saml2 into the inventory role. We should be able to just skip the role based on the inventory_app_saml2_enabled variable.
In the longer-term, #1473 will address the tech debt and remove the need for the saml2 role.
I'm going to rename this issue so it's more clear as to what we're after.
adborden
changed the title
Incorporate SAML2 role into the inventory ansible role
Enable optional native login in the inventory ansible role
Apr 16, 2020
User Story
In order to enable deployment and testing of inventory CKAN in non-BSP environments, we want the setup of local vs SAML authentication to be configurable with a variable.
Acceptance Criteria
inventory_ckan_saml2_enabled: false
WHEN the
inventory.yml
playbook is runTHEN the environment is configured with CKAN's native user/password login
inventory_ckan_saml2_enabled: true
WHEN the
inventory.yml
playbook is runTHEN the environment is configured with SAML2 authentication
Details
Similar work has already been done for catalog.
Will need to
The text was updated successfully, but these errors were encountered: