vertx / io.vertx.ext.auth

Package io.vertx.ext.auth

Types

AbstractUser

abstract class AbstractUser : User, ClusterSerializable

Useful base class for implementing a User object.

This class handles the caching logic so you can concentrate on the actual authorisation logic.

Just implement the abstract methods in your concrete sub-class.

ChainAuth

interface ChainAuth : AuthProvider

Chain several auth providers as if they were one. This is useful for cases where one want to authenticate across several providers, for example, database and fallback to passwd file.

KeyStoreOptionsConverter

open class KeyStoreOptionsConverter

Converter for io.vertx.ext.auth.KeyStoreOptions. NOTE: This class has been automatically generated from the io.vertx.ext.auth.KeyStoreOptions original class using Vert.x codegen.

PRNG

open class PRNG : VertxContextPRNG

Wrapper around secure random that periodically seeds the PRNG with new entropy. To avoid entropy exhaustion the entropy is only refreshed if the PRNG is used. This introduces a new variable which reduces the probability of cracking the random number generator.

PubSecKeyOptionsConverter

open class PubSecKeyOptionsConverter

Converter for io.vertx.ext.auth.PubSecKeyOptions. NOTE: This class has been automatically generated from the io.vertx.ext.auth.PubSecKeyOptions original class using Vert.x codegen.

SecretOptionsConverter

open class SecretOptionsConverter

Converter for io.vertx.ext.auth.SecretOptions. NOTE: This class has been automatically generated from the io.vertx.ext.auth.SecretOptions original class using Vert.x codegen.

VertxContextPRNG

interface VertxContextPRNG

A secure non blocking random number generator isolated to the current context. The PRNG is bound to the vert.x context and setup to close when the context shuts down.

When applicable, use of VertxContextPRNG rather than create new PRNG objects is helpful to keep the system entropy usage to the minimum avoiding potential blocking across the application.

The use of VertxContextPRNG is particularly appropriate when multiple handlers use random numbers.