identity-server.samples

Sample projects implemented to show third-party developers how to connect to the authentication system in various languages and platforms. All the sample projects talk to the island.is staging for the authentication system. All the projects are setup so that to change the connection from the staging server to the real authentication system you only need to change environment variables.

NestJS

1. A service with an implemented “Jwt” auth-guard with a registered audience to island.is authentication service that can be added as a guard to controllers or functions, meaning that it´s only possible for tokens issued by island.is authentication service with a specific scope to call those controllers or functions.
   It comes implemented with the OpenApi specification using Swagger and the Swagger Authorization functionality so that you can generate tokens from island.is authentication service using Swagger and call the functions in the service without getting a 401 code.
   Access it by clicking here

2. A service that is not protected by an oidc-provider but implements a call to a demo service that uses island.is authentication service as an oidc-provider. To do that the service needs to call the island.is authentication service to get a “client_credentials” token. The purpose of this service is to show the implementation of how to get a “client_credentials” token from the island.is authentication service using NestJS.
   It comes implemented with the OpenApi specification using Swagger but not the Swagger Authorization functionality.
   Access it by clicking here

NetCore

1. A service that uses island.is authentication service as an oidc-provider with a registered audience, meaning that it´s only possible for tokens issued by island.is authentication service with a specific scope to call the controllers or functions in the service marked with the “Authorization” flag.
   It comes implemented with the OpenApi specification using Swagger and the Swagger Authorization functionality so that you can generate tokens from island.is authentication service using Swagger and call the functions in the service without getting a 401 code.
   Access it by clicking here

2. A service that is not protected by an oidc-provider but implements a call to a demo service that uses island.is authentication service as an oidc-provider. To do that the service needs to call the island.is authentication service to get a “client_credentials” token. The purpose of this service is to show the implementation of how to get a “client_credentials” token from the island.is authentication service using NestJS.
   It comes implemented with the OpenApi specification using Swagger but not the Swagger Authorization functionality.
   Access it by clicking here

Angular

An angular client that demonstrates how you can generate and use the token from island.is authentication service. It also demonstrates how you can then use that token to call a function in one of the demo services in .NetCore or NestJS.
Access it by clicking here

React

A react client that demonstrates how you can generate and use the token from island.is authentication service. It also demonstrates how you can then use that token to call a function in one of the demo services in .NetCore or NestJS.
Access it by clicking here

Next.js

A next.js client that demonstrates how you can generate and use the token from island.is authentication service. It also demonstrates how you can use that token to call a function in one of the demo services in .NetCore or NestJS.
Access it by clicking here