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

KEYCLOAK-16851 revised overview chapter to create more findable titles

Browse source
This commit is contained in:
Andy Munro 2021-03-18 17:01:43 -04:00 committed by Marek Posolda
parent 1177318260
commit b32f5b9bf7
4 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
server_admin/topics/overview.adoc
View file

@ -1,4 +1,4 @@
== Overview
== {project_name} features and concepts
{project_name} is a single sign on solution for web apps and RESTful web services. The goal of {project_name}
is to make security simple so that it is easy for application developers to secure the apps and services they have deployed

5
server_admin/topics/overview/concepts.adoc
View file

@ -1,8 +1,7 @@
=== Core Concepts and Terms
=== Core concepts and terms
There are some key concepts and terms you should be aware of before attempting to use {project_name} to secure your web applications
and REST services.
Consider these core concepts and terms before attempting to use {project_name} to secure your web applications and REST services.
users::
Users are entities that are able to log into your system. They can have attributes associated with themselves like email,

2
server_admin/topics/overview/features.adoc
View file

@ -1,6 +1,8 @@
=== Features
{project_name} provides the following features:
* Single-Sign On and Single-Sign Out for browser applications.
* OpenID Connect support.
* OAuth 2.0 support.

4
server_admin/topics/overview/how.adoc
View file

@ -1,11 +1,11 @@
=== How Does Security Work?
=== Basic {project_name} operations
{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/connect/[OpenID Connect]
or link:http://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
server where they enter their credentials. This 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
signed. These tokens can have identity information like username, address, email, and other profile data. They can also
hold permission data so that applications can make authorization decisions. These tokens can also be used to make secure