2014-02-14 14:50:49 +00:00
|
|
|
<chapter id="Migration_from_older_versions">
|
|
|
|
|
<title>Migration from older versions</title>
|
|
|
|
|
<sect1>
|
2014-02-21 15:16:12 +00:00
|
|
|
<title>Migrating from 1.0 Alpha 2 to Alpha 3</title>
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem>
|
|
|
|
|
SkeletonKeyToken, SkeletonKeyScope, SkeletonKeyPrincipal, and SkeletonKeySession have been renamed to:
|
|
|
|
|
AccessToken, AccessScope, KeycloakPrincipal, and KeycloakAuthenticatedSession respectively.
|
|
|
|
|
</listitem>
|
2014-02-25 00:58:54 +00:00
|
|
|
<listitem>
|
|
|
|
|
ServleOAuthClient.getBearerToken() method signature has changed. It now returns an AccessTokenResponse
|
|
|
|
|
so that you can obtain a refresh token too.
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
Adapters now check the access token expiration with every request. If the token is expired, they will
|
|
|
|
|
attempt to invoke a refresh on the auth server using a saved refresh token.
|
|
|
|
|
</listitem>
|
2014-03-12 15:58:35 +00:00
|
|
|
<listitem>
|
|
|
|
|
Subject in AccessToken has been changed to the User ID.
|
|
|
|
|
</listitem>
|
2014-02-21 15:16:12 +00:00
|
|
|
</itemizedlist>
|
|
|
|
|
</sect1>
|
|
|
|
|
<sect1>
|
|
|
|
|
<title>Migrating from 1.0 Alpha 1 to Alpha 2</title>
|
2014-02-14 14:50:49 +00:00
|
|
|
<itemizedlist>
|
2014-02-18 20:30:32 +00:00
|
|
|
<listitem>
|
|
|
|
|
DB Schema has changed. We don't have any data migration utilities yet as of Alpha 2.
|
|
|
|
|
</listitem>
|
2014-02-14 14:50:49 +00:00
|
|
|
<listitem>
|
|
|
|
|
JBoss and Wildfly adapters are now installed via a JBoss/Wildfly subsystem. Please review the adapter
|
|
|
|
|
installation documentation. Edits to standalone.xml are now required.
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
There is a new credential type "secret". Unlike other credential types, it is stored in plain text in
|
|
|
|
|
the database and can be viewed in the admin console.
|
|
|
|
|
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
There is no longer required Application or OAuth Client credentials. These client types are now
|
|
|
|
|
hard coded to use the "secret" credential type.
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem>
|
|
|
|
|
Because of the "secret" credential change to Application and OAuth Client, you'll have to update
|
|
|
|
|
your keycloak.json configuration files and regenarate a secret within the Application or OAuth Client
|
|
|
|
|
credentials tab in the administration console.
|
|
|
|
|
</listitem>
|
|
|
|
|
</itemizedlist>
|
|
|
|
|
</sect1>
|
|
|
|
|
</chapter>
|
