Identica: Credential provider

Description

Credential Provider is the official Identica provider for password-based accounts.

It gives your network a familiar credential login path while still keeping everything inside Identica’s provider system. Players can register with a credential, log in with it later, change it when needed, and protect the account with additional verification methods if your setup requires it.

Dependencies & Information

• Platform
  Credential Provider is currently a Velocity/BungeeCord provider and should be installed on your proxy together with Identica.

• Java
  The provider works exclusively on Java 21 and higher.

• Requires Identica
  Credential Provider is not a standalone authentication plugin. It requires the Identica core to be installed and configured.

Capabilities

Capabilities describe which parts of the Identica provider system this resource supports. They help you understand what Credential Provider can participate in when it is installed alongside the Identica core.

• Credential Authentication
  Credential Provider allows players to authenticate with a password-style credential through Identica. It provides the familiar login flow while still keeping sessions, provider links, and account handling inside the Identica system.

• Credential Registration
  Players can create a credential account directly through the provider. Registration can require the credential to be repeated, and the accepted credential format can be controlled through configurable rules such as length, uppercase letters, lowercase letters, numbers, and special characters.

• Credential Management
  Players can change their credential after logging in, while administrators can manage credential accounts through protected admin commands when needed.

• Provider Migration
  Credential Provider supports migration from other Identica providers into Credential Provider. It can also participate in migrations away from Credential Provider when your network allows another provider to become the account’s new primary method.

• Verification Methods
  Credential Provider works with Identica verification methods such as TOTP-based 2FA. This means a credential account can be protected by additional confirmation, and more verification methods can be added through Identica or separate addons.

• Attempt Protection
  Credential Provider includes configurable failed-attempt protection. Your network can show remaining-attempt warnings, temporarily lock repeated failed attempts, and tune the limits to match your security needs.

What Credential Provider Gives You

Credential Provider is useful when you want a reliable password-based account path inside Identica.

It gives players a clear way to register, log in, and manage their credential without leaving the Identica ecosystem. The provider handles credential-specific behavior such as password rules, hashing, verification, failed-attempt protection, and migration steps, while Identica keeps the wider account and provider structure consistent.

This gives server owners a practical fallback or primary account method for players who should authenticate with credentials, while still leaving room for other providers to exist beside it.

Who This Provider Is For

Credential Provider is a good fit for networks that use Identica and want a traditional credential-based login method.

It is especially useful if you want players to register with a password, protect accounts with TOTP or other verification methods, control credential strength rules, limit repeated failed attempts, or let players migrate between credential-based access and other Identica providers.

If your setup uses multiple Identica providers, Credential Provider can work alongside them as the dependable password-based path for players who need it.

Configuration

Most networks can start with the default configuration.

Advanced setups can adjust registration rules, credential confirmation, change-password behavior, hashing algorithms, automatic hash upgrades, failed-attempt protection, messages, commands, and replication cache namespaces when needed. Full setup details and field-by-field configuration notes are available in the Documentation.