unsecure url has principal
KEYCLOAK-2550 Typo in userguide KEYCLOAK-1928 Kerberos working with IBM JDK KEYCLOAK-1928 Remove sun.jdk.jgss module KEYCLOAK-1928 Fix kerberos with adapter on JDK7 KPR-147 - Initial login scenarios around admin password - test KEYCLOAK-2561 Fix issues with blank password KEYCLOAK-2559 Missing add/remove button for 'Valid Redirect URIs' in a client settings form Added simple test for JPA performance (with many users). Fixed "re-import" operation logging. Fixed for Timer.saveData() Fixed for Timer.saveData() ManyUsersTest: ArrayList --> LinkedList Fix AbstractUserTest Fix parentheses in login page object Add tests for IDP initiated login KEYCLOAK-1040 Allow import of realm keys (like we do for SAML) KEYCLOAK-2556 Remove required for client create root url and saml endpoint KEYCLOAK-2555 ForbiddenException when importing test realm or creating test user KEYCLOAK-2553 Unexpected form behavior while creating a client KEYCLOAK-2551 Broken navigation links while creating/editing a Client Mapper
This commit is contained in:
1 parent
a0696fcb97
commit
37584a24e0
87 files changed
+1683
-262
No files matched your search
@@ -0,0 +1,12 @@
|
||||
<chapter>
|
||||
<title>KeycloakSecurityContext</title>
|
||||
<para>
|
||||
The <literal>KeycloakSecurityContext</literal> interface is available if you need to look at the access token directly. This context is also useful if you need to
|
||||
get the encoded access token so you can make additional REST invocations. In servlet environments it is available in secured invocations as an attribute in HttpServletRequest.
|
||||
Or, it is available in secure and insecure requests in the HttpSession for browser apps.
|
||||
<programlisting>
|
||||
httpServletRequest.getAttribute(KeycloakSecurityContext.class.getName());
|
||||
httpServletRequest.getSession().getAttribute(KeycloakSecurityContext.class.getName());
|
||||
</programlisting>
|
||||
</para>
|
||||
</chapter>
|
||||
@@ -155,7 +155,7 @@ Authorization: basic BASE64(client-id + ':' + client-secret)
|
||||
</para>
|
||||
<para>
|
||||
To retrieve the Adapter Configuration then do a HTTP GET to:
|
||||
<literal><KEYCLOAK URL>//realms/<realm>/clients-registrations/installation/<client id></literal>
|
||||
<literal><KEYCLOAK URL>//realms/<realm>/clients-registrations/install/<client id></literal>
|
||||
</para>
|
||||
<para>
|
||||
No authentication is required for public clients. This means that for the JavaScript adapter you can
|
||||
|
||||
Reference in new issue
Block a user