# svelte-oidc
An Oidc Client Component for Svelte.
[Try out the demo](https://darrelopry.com/svelte-oidc/)
## Getting Started
Setup an OIDC Sever
* https://www.ory.sh/
* https://www.keycloak.org/
* https://www.okta.com/
* http://auth0.com/
Get the authority and client_id
`npm install @dopry/svelte-oidc`
App.svelte
```svelte
# App.svelte
import {
OidcContext,
LoginButton,
LogoutButton,
RefreshTokenButton,
authError,
accessToken,
idToken,
isAuthenticated,
isLoading,
login,
logout,
userInfo,
} from '@dopry/svelte-oidc';
const metadata = {
// added to overcome missing value in auth0 .well-known/openid-configuration
// see: https://github.com/IdentityModel/oidc-client-js/issues/1067
// see: https://github.com/IdentityModel/oidc-client-js/pull/1068
end_session_endpoint: `process.env.OIDC_ISSUER/v2/logout?client_id=process.env.OIDC_CLIENT_ID`,
};
LoginLogoutRefreshToken
isLoading: {$isLoading}
isAuthenticated: {$isAuthenticated}
authToken: {$accessToken}
idToken: {$idToken}
userInfo: {JSON.stringify($userInfo, null, 2)}
authError: {$authError}
```
## Sapper/SSR
This component does not natively support SSR nor can it be used for authentication in server side rendered contexts. It
can be used within SSR applications as long as it is acceptable for all authentication to be client side. In order to
use for client side auth in an SSR application you will need to ensure it is not rendered server side as follows.
```
{#if process.browser} ..... {/if}
```
## SvelteKit/SSR
Same as what is needed for Sapper (see above section). To do this, we need to import in the `script` section:
```
import { browser } from '$app/env';
```
And in the `main`:
```
{#if browser} ..... {/if}
```
## Contributing
Contributors are Welcome. There is a lot of value in a vendor neutral OIDC component for use by the Svelte and Sapper
community. As a developer and product manager, I have needed to switch between Okta, Auth0, KeyCloak, IdentityServer,
and Ory on multiple occasions. Vendor specific libraries are usually riddled with vendor specific assumptions that make
the migration hard.
**How to Help!**
* Better Documentation
* Helping with the Issue Queue (support, good bug report, resolving bugs)
* SSR Support
* Automated Testing of all major identity providers
**PRs Welcome!**
## Docs
### Components
* OidcContext - component to initiate the OIDC client. You only need one instance in your DOM tree at the root.
Attributes:
* issuer - OIDC Authority/issuer/base url for .well-known/openid-configuration
* client_id - OAuth ClientId
* redirect_uri - default: window.location.href
* post_logout_redirect_uri - override the default url that OIDC will redirect to after logout. default: window.location.href
* metadata - set default metadata or metadata missing from authority.
* extraOptions - An object of extra options that will be passed to the underlying OpenID Connect client. Valid values are available [here](https://github.com/IdentityModel/oidc-client-js/wiki#other-optional-settings).
* LoginButton - log out the current context
Attributes:
* preserve_route - tell the callback handler to return to the current url after login. default: true
* callback_url - override the context callback_url
* LogoutButton - log in the current context
Attributes:
* logout_url - override the context logout_url
* RefreshTokenButton - refresh the current token
### Functions
* login(oidcPromise, preseveRoute = true, callback_url = null) - begin a user login.
* logout(oidcPromise, logout_url = null) - logout a user.
* refreshToken(oidcPromise) - function to refresh a token.
### Stores
* isLoading - if true OIDC Context is still loading.
* isAuthenticated - true if user is currently authenticated
* accessToken - access token for connecting to apis.
* idToken - identity token for getting user info easily.
* userInfo - the currently logged in user's info from OIDC userInfo endpoint
* authError - the last authentication error.
### Constants
* OIDC_CONTEXT_CALLBACK_URL
* OIDC_CONTEXT_CLIENT_PROMISE - key for the OIDC client in setContext/getContext.
* OIDC_CONTEXT_LOGOUT_URL,
## Development
npm run showcase:dev
## Release
use semver
1. npm publish
2. npm run showcase:build
3. npm run showcase:publish