keycloak-js validate token without a refresh token

[clayrisser]

Description

Currently, the keycloak-js client requires both a token and a refresh token to be provided for initialization. However, there are scenarios where someone may have only a token without a refresh token, and would still like to initialize the client using this token.

Discussion

No response

Motivation

By allowing users to initialize the keycloak-js client with a token only, without the requirement for a refresh token, we can provide greater flexibility and convenience in scenarios where a refresh token may not be readily available. This can improve the user experience and make it easier for developers to integrate Keycloak authentication and authorization into their applications. Additionally, this can enable support for scenarios such as single sign-on with limited token lifetimes or use cases where refresh tokens are not issued by the identity provider.

Details

No response

[clayrisser]

Just opened a pull request to support this.