Backend API. Server-side code: this runs in a Codename One backend, not in the app on the device.

package com.codename1.backend.security.core.userdetails

Users as the security layer sees them: UserDetails, the UserDetailsService a chain authenticates against, and an in-memory store.

Types

class InMemoryUserDetailsManagerUsers kept in memory: for a demonstration, a test, or a server whose handful of accounts is part of its configuration.
class JdbcUserDetailsManagerUsers kept in the server’s database, in the cn1_users and cn1_authorities tables of SecuritySchema.
class UserThe UserDetails the runtime provides.
interface UserDetailsA user as the security layer needs to know one: a name, an encoded password, what it has been granted, and whether the account may be used.
interface UserDetailsManagerA UserDetailsService that can also create, change and delete its users.
interface UserDetailsPasswordServiceStores a password re-encoded on sign-in, for a user store that wants old hashes replaced as their owners come back.
interface UserDetailsServiceFinds a user by the name typed at sign-in.
class UsernameNotFoundExceptionA UserDetailsService has no user of the name it was asked for.