libre.sh/keycloak-scim
2
0
Fork 0
Code Issues 14 Pull requests Releases Packages Activity Actions 6

added missing "allow ecp flow" field (#20713)

Browse source 
fixes: #20673
This commit is contained in:
Erik Jan de Wit 2023-06-12 12:46:03 +02:00 committed by GitHub
parent ed473da22b
commit 8d2dbbe6ad
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
js/apps/admin-ui/public/locales/en/clients-help.json
View file

@ -22,6 +22,7 @@
"includeAuthnStatement": "Should a statement specifying the method and timestamp be included in login responses?", "includeAuthnStatement": "Should a statement specifying the method and timestamp be included in login responses?",
"includeOneTimeUseCondition": "Should a OneTimeUse Condition be included in login responses?", "includeOneTimeUseCondition": "Should a OneTimeUse Condition be included in login responses?",
"optimizeLookup": "When signing SAML documents in REDIRECT binding for SP that is secured by Keycloak adapter, should the ID of the signing key be included in SAML protocol message in <Extensions> element? This optimizes validation of the signature as the validating party uses a single key instead of trying every known key for validation.", "optimizeLookup": "When signing SAML documents in REDIRECT binding for SP that is secured by Keycloak adapter, should the ID of the signing key be included in SAML protocol message in <Extensions> element? This optimizes validation of the signature as the validating party uses a single key instead of trying every known key for validation.",
"allowEcpFlow": "This client is allowed to use ECP flow for authenticating users.",
"signDocuments": "Should SAML documents be signed by the realm?", "signDocuments": "Should SAML documents be signed by the realm?",
"signAssertions": "Should assertions inside SAML documents be signed? This setting is not needed if document is already being signed.", "signAssertions": "Should assertions inside SAML documents be signed? This setting is not needed if document is already being signed.",
"signatureAlgorithm": "The signature algorithm to use to sign documents. Note that 'SHA1' based algorithms are deprecated and can be removed in the future. It is recommended to stick to some more secure algorithm instead of '*_SHA1'", "signatureAlgorithm": "The signature algorithm to use to sign documents. Note that 'SHA1' based algorithms are deprecated and can be removed in the future. It is recommended to stick to some more secure algorithm instead of '*_SHA1'",

1
js/apps/admin-ui/public/locales/en/clients.json
View file

@ -375,6 +375,7 @@
"includeAuthnStatement": "Include AuthnStatement", "includeAuthnStatement": "Include AuthnStatement",
"includeOneTimeUseCondition": "Include OneTimeUse Condition", "includeOneTimeUseCondition": "Include OneTimeUse Condition",
"optimizeLookup": "Optimize REDIRECT signing key lookup", "optimizeLookup": "Optimize REDIRECT signing key lookup",
"allowEcpFlow": "Allow ECP flow",
"signDocuments": "Sign documents", "signDocuments": "Sign documents",
"signAssertions": "Sign assertions", "signAssertions": "Sign assertions",
"signatureKeyName": "SAML signature key name", "signatureKeyName": "SAML signature key name",

4
js/apps/admin-ui/src/clients/add/SamlConfig.tsx
View file

@ -131,6 +131,10 @@ export const SamlConfig = () => {
)} )}
label="optimizeLookup" label="optimizeLookup"
/> />
<Toggle
name={convertAttributeNameToForm("attributes.saml.allow.ecp.flow")}
label="allowEcpFlow"
/>
</FormAccess> </FormAccess>
); );
}; };