libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases 1 Packages Activity Actions

[docs] Update saml.xml.org link from http to https

Browse source 
closes keycloak/keycloak#21317
This commit is contained in:
Joshua Sorah 2023-06-29 10:06:58 -04:00 committed by Alexander Schwartz
parent f695eeaa44
commit e945a056bb
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/documentation/securing_apps/topics/overview/supported-protocols.adoc
View file

@ -26,7 +26,7 @@ the request.
==== SAML 2.0 ==== SAML 2.0
link:http://saml.xml.org/saml-specifications[SAML 2.0] is a similar specification to OIDC but a lot older and more mature. It has its roots in SOAP and the plethora link:https://saml.xml.org/saml-specifications[SAML 2.0] is a similar specification to OIDC but a lot older and more mature. It has its roots in SOAP and the plethora
of WS-* specifications so it tends to be a bit more verbose than OIDC. SAML 2.0 is primarily an authentication protocol of WS-* specifications so it tends to be a bit more verbose than OIDC. SAML 2.0 is primarily an authentication protocol
that works by exchanging XML documents between the authentication server and the application. XML signatures and encryption are used to verify requests and responses. that works by exchanging XML documents between the authentication server and the application. XML signatures and encryption are used to verify requests and responses.

2
docs/documentation/server_admin/topics/overview/how.adoc
View file

@ -3,7 +3,7 @@
{project_name} is a separate server that you manage on your network. Applications are configured to point to and {project_name} is a separate server that you manage on your network. Applications are configured to point to and
be secured by this server. {project_name} uses open protocol standards like link:https://openid.net/developers/how-connect-works/[OpenID Connect] be secured by this server. {project_name} uses open protocol standards like link:https://openid.net/developers/how-connect-works/[OpenID Connect]
or link:http://saml.xml.org/saml-specifications[SAML 2.0] to secure or link:https://saml.xml.org/saml-specifications[SAML 2.0] to secure
your applications. Browser applications redirect a user's browser from the application to the {project_name} authentication your applications. Browser applications redirect a user's browser from the application to the {project_name} authentication
server where they enter their credentials. This redirection is important because users are completely isolated from applications and server where they enter their credentials. This redirection is important because users are completely isolated from applications and
applications never see a user's credentials. Applications instead are given an identity token or assertion that is cryptographically applications never see a user's credentials. Applications instead are given an identity token or assertion that is cryptographically

2
docs/documentation/server_admin/topics/sso-protocols/con-saml.adoc
View file

@ -4,7 +4,7 @@
=== SAML === SAML
[role="_abstract"] [role="_abstract"]
link:http://saml.xml.org/saml-specifications[SAML 2.0] is a similar specification to OIDC but more mature. It is descended from SOAP and web service messaging specifications so is generally more verbose than OIDC. SAML 2.0 is an authentication protocol that exchanges XML documents between authentication servers and applications. XML signatures and encryption are used to verify requests and responses. link:https://saml.xml.org/saml-specifications[SAML 2.0] is a similar specification to OIDC but more mature. It is descended from SOAP and web service messaging specifications so is generally more verbose than OIDC. SAML 2.0 is an authentication protocol that exchanges XML documents between authentication servers and applications. XML signatures and encryption are used to verify requests and responses.
In general, SAML implements two use cases. In general, SAML implements two use cases.