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
So I have to convert them all from snake case to camel case for python3-saml, but for one exception that doesn't follow the rule. Anyway.. figured I'd grumble. haha
The text was updated successfully, but these errors were encountered:
I think I can fix that and support both NameIDFormat and NameIdFormat.
And related to the use of 'en-US' as country code, I see its use in many many places, for example see this page where Metadata elements are described, it uses 'en-US'
but you can use whatever lang code as part of the info for the Organizational Data you inject in your settings.
So every setting key name is CamelCase except
NameIDFormat
. Is there a particular reason for this?I'm building a connector and due to ES, the settings need to be snake_case: https://www.elastic.co/guide/en/ecs/current/ecs-guidelines.html#_guidelines_for_field_names
So I have to convert them all from snake case to camel case for python3-saml, but for one exception that doesn't follow the rule. Anyway.. figured I'd grumble. haha
The text was updated successfully, but these errors were encountered: