npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

nli-keycloak-auth

v1.2.0

Published

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.0.3. The library is published to the private NLI npm-repository.

Downloads

2

Readme

NliKeycloakAuth

This library was generated with Angular CLI version 8.0.3. The library is published to the private NLI npm-repository.

Running unit tests

Run ng test nli-keycloak-auth to execute the unit tests via Karma.

Usage

You need to import the KeycloakAuthModule preferable in your app.module.ts. Then you have to execute the forRoot(baseAuthConfig: BaseAuthConfig, keycloakConfigServiceProvider?: Provider) Method. To execute the method you have to provide the BaseAuthConfig. Furthermore you can provide a provider for the KeyCloakConfigService. If not the default provider is used which will call the /config Rest-Endpoint.

Config Rest-Endpoint

The default keycloak configuration provider is a Rest-Endpoint called by this angular-framework. The Endpoint is called at /config and its structure is described at KeycloakConfig. These are:

    oauthServerUrl: string;
    keycloakRealm: string;
    disableAuth?: boolean;
    disableHttps?: boolean;

Here is an example implementation of this endpoint with spring boot, where the configuration is extracted into application.yml:

The Controller:

@RestController
@RequiredArgsConstructor
public class ConfigController {
	private final Config config;

	@RequestMapping(value = "/config", method = RequestMethod.GET, produces = "application/json")
	public Config getConfig() {
		return config;
	}
}

The provided configuration Pojo:

@Component
@Data
public class Config {
	@Value("${keycloak.auth-server-url:}")
	private String oauthServerUrl;
	@Value("${keycloak.realm:}")
	private String keycloakRealm;
	@Value("#{environment.acceptsProfiles('secure') ? false : true }")
	private boolean disableAuth;
	@Value("${disable-https-for-keycloak: false}")
	private boolean disableHttps;
}

The application.yml:

spring:
  profiles:
    active:
      - secure
keycloak:
  auth-server-url: http://localhost:8777/auth
  realm: NLI
disable-https-for-keycloak: true

Since the spring-boot backend needs the same keycloak configuration, we can avoid duplication of the configuration. (The backend uses the module af50-authorization which uses keycloak-spring-boot-2-adapter which can be configured by the same yml.)

KeycloakConfigService

If you want to set another provider you have to do the following steps: Create the service an implement the KeycloakConfigService interface. Then you hve to set the provider in the forRoot method like this MyModule.forRoot(baseAuthConfig, {provide: KeycloakConfigServiceInj, useClass: YourImplementationOfKeycloakConfigService})

BaseAuthConfig

export interface BaseAuthConfig {
    clientId: string;
    disableAuth?: boolean;
    loginTarget: string;
    logoutTarget: string;
    loginRedirectAppendix?: string;
    logoutRedirectAppendix?: string;
    manualLogin?: boolean;
}

| configuration name | accepted values | meaning | optional | default value | |------------------------|-----------------|----------------------------------------------------------------------------------------------------------------------|----------|----------------| | clientId | string | the clientId from the keycloak server | no | / | | disableAuth | true,false | always return true if authentication is required | yes | false | | loginTarget | string | where to redirect if login method when disableAuth is true | yes | loginredirect | | logoutTarget | string | where to redirect when logout method when disableAuth is true | yes | logoutredirect | | loginRedirectAppendix | string | route where the keycloak will redirect you after login | yes | loginredirect | | logoutRedirectAppendix | string | route where the keycloak will redirect you after logout | yes | logoutredirect | | manualLogin | true, false | when activated, the keycloak login page will not be loaded automatically. You have to call the login method manually | yes | false |