Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use datagov saml2auth #814

Merged
merged 1 commit into from
Feb 18, 2025
Merged

use datagov saml2auth #814

merged 1 commit into from
Feb 18, 2025

Conversation

FuhuXia
Copy link
Member

@FuhuXia FuhuXia commented Feb 18, 2025

We have a few customization done on saml2auth. GSA/ckanext-saml2auth@ckan-2-11...ckan-2-11-datagov

@FuhuXia FuhuXia requested a review from a team February 18, 2025 15:01
@jbrown-xentity
Copy link
Contributor

@FuhuXia it seems like we're indefinitely maintaining this fork. Should we standardize on a clear branch; say datagov? And then make that the default branch with branch protections? That way it's more clear when we go to the repository what we've actually deployed/using, instead of having to go to inventory and/or catalog to find the commit or branch that is being used...

@FuhuXia
Copy link
Member Author

FuhuXia commented Feb 18, 2025

@FuhuXia it seems like we're indefinitely maintaining this fork. Should we standardize on a clear branch; say datagov? And then make that the default branch with branch protections? That way it's more clear when we go to the repository what we've actually deployed/using, instead of having to go to inventory and/or catalog to find the commit or branch that is being used...

We will, when catalog is on ckan 2.11 too.

@FuhuXia FuhuXia merged commit d1e3081 into main Feb 18, 2025
11 checks passed
@FuhuXia FuhuXia deleted the saml2auth branch February 18, 2025 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants