Elements Manual
Elements 3 Manual
Elements 3 Manual
  • Welcome 👋
  • QUICK START
    • Elements in Five Minutes or Less
    • Accessing the Web UI (CRM)
    • Creating A User
  • General
    • General Concepts
    • N-Tier Architecture
    • Security Model
  • Core Features
    • Core API Overview
    • Sessions
    • Applications
    • Users and Profiles
    • Digital Goods
    • Progress and Missions
    • Leaderboards
    • Matchmaking
    • Followers
    • Friends
    • Reward Issuance
    • Save Data
    • Schemas and Metadata Specifications
    • Queries
      • Base Query Syntax
      • Boolean Queries
      • Object Graph Navigation
      • Advanced Operators
        • .ref
        • .name
    • Custom Code
      • Element Structure
      • RESTful APIs
      • Websockets
    • Auth Schemes
      • OIDC
      • OAuth2
  • Web 3
    • Omni Chain Support
    • Vaults
    • Wallets
    • Smart Contracts
      • Smart Contracts: Ethereum
      • Smart Contracts: Flow
      • Smart Contracts: Solana
      • Smart Contracts: Neo
  • CONFIGURATION
    • Direct Database Access and Batch Configuration
    • Batch Samples
      • Item Upload Bash Script Sample
      • Mission Upload Bash Script Sample
  • RESTful APIs
    • Swagger and Swagger UI
    • API Specification
      • /application
      • /application/configuration
      • /auth
      • /auth_scheme
        • /custom
        • /oauth2
        • /oidc
      • /blockchain
      • /followee
      • /follower
      • /friend
      • /google
      • /index
      • /inventory
      • /item
      • /large_object
      • /leaderboard
      • /rank
      • /score
      • /match
      • /mission
      • /progress
      • /reward_issuance
      • /schedule
      • /notification
      • /profile
      • /save_data
      • /metadata_spec
      • /mock_session
      • /session
      • /health
      • /version
      • /signup
      • /user
    • Javadocs
  • Releases
    • 3.1 Release Notes
Powered by GitBook
On this page
  • 🔐 Security Integration for Custom APIs
  • Additional Fixes and Enhancements
  1. Releases

3.1 Release Notes

Release notes for Verion 3.1

This release addresses a major issue introduced in version 3.0 related to service layer scoping. In 3.1, we’ve refactored the way services are accessed and scoped, ensuring consistent lifecycle behavior across the platform. This resolves previous issues where services were incorrectly shared or not instantiated as expected in custom environments.

These changes make it easier to manage dependency lifecycles and improve the developer experience when building custom extensions or services within the Elements platform.

🔐 Security Integration for Custom APIs

Custom RESTful APIs can now opt into the Elements security model by setting the following property in your configuration:

    @ElementDefaultAttribute("true")
    public static final String AUTH_ENABLED = "dev.getelements.elements.auth.enabled";

When enabled, this feature enforces full parity with the core Elements authentication system. Your custom endpoints will inherit:

  • Session token verification

  • User authentication

  • Permission enforcement

This allows developers to extend the backend securely without duplicating or rewriting auth logic.

Additional Fixes and Enhancements

  • Improved validation and error reporting for service injection configuration

  • Extended documentation for custom API and middleware development

  • Minor performance optimizations in the request routing pipeline

  • Fixed a bug related to deleting user accounts

  • Added OAuth 2.0 support for Steam APIs

PreviousJavadocs

Last updated 22 days ago