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

Fix error if group claim type does not exist in the trust #207

Merged
merged 4 commits into from
Apr 15, 2024

Conversation

Yvand
Copy link
Owner

@Yvand Yvand commented Apr 11, 2024

CHANGELOG

@Yvand Yvand merged commit ce3ae05 into dev Apr 15, 2024
4 checks passed
@Yvand Yvand deleted the fix-error-if-no-group-claim-type branch April 15, 2024 07:44
Yvand added a commit that referenced this pull request May 13, 2024
* Update AssemblyInfo.cs

* Update GlobalSettings.ascx

* Update GlobalSettings.ascx

* Fix error if group claim type does not exist in the trust (#207)

* fix #203

* Update CHANGELOG.md

* update test in GroupIdentifierEncodedValuePrefix

* delete group claim type if None is selected

* Ignore case when comparing claim types (#205)

* ignore case when comparing claim types

* Update CHANGELOG.md

* Update CHANGELOG.md

* add server-side member NoValueSelected to test "None"

* Add property max search results count (#211)

* initial work

* work

* Fix uninitialized properties (#212)

* Update LDAPProviderConfiguration.cs

* remove deprecated pipelines

* test if ClaimsPrincipal.Identity is null

* Add helper methods to get/delete a directory connection in the configuration

* ask for confirmation before deleting connection

* fix repository name hosting the reusable workflows

* update build workflow
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.

[LDAPCPSE] After adding a LDAPS connection as second option, going to global config page will error out
1 participant