Download the PHP package horde/token without Composer

On this page you can find all versions of the php package horde/token. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of horde/token

Informations about the package token

Horde Token System

(AI generated on 2025 April 18th)

Overview

The Horde Token system is a core component of the Horde Framework that provides secure token generation, validation, and management functionality. It is used across various Horde applications for authentication, session management, and secure URL generation.

Key Features

Token Types

  1. URL Tokens

    • Used for secure URL generation and validation
    • Configurable lifetime (default: 30 seconds)
    • HMAC-based validation for security

  2. Authentication Tokens

    • Used for session management and authentication
    • Supports various authentication backends
    • Configurable session timeout
  3. CSRF Protection Tokens
    • Prevents Cross-Site Request Forgery attacks
    • Automatically generated and validated for forms

Storage Backends

The token system supports multiple storage backends:

  1. SQL Storage

    • Supports various SQL databases:
      • PostgreSQL
      • MySQL/MariaDB
      • SQLite
    • Schema for SQL storage:

  2. File Storage

    • Simple file-based storage
    • Suitable for single-server deployments
    • Easy to backup and maintain
    • Configuration example:
  3. MongoDB Storage
    • NoSQL storage option
    • High scalability
    • Document-based storage
    • Configuration example:

Configuration

The token system is configured through Horde's main configuration file (conf.php):

Security Features

  1. Token Generation

    • Cryptographically secure random token generation
    • Unique token IDs for each token address
    • Timestamp-based expiration

  2. Token Validation

    • HMAC-based validation for URL tokens
    • Timestamp validation for expiration
    • Address-based token lookup
  3. Storage Security
    • Secure storage across all backends
    • Automatic token cleanup
    • Protection against token reuse

Integration

Usage in Applications

The token system is integrated into various Horde applications:

  1. Authentication

    • Session token management
    • Secure login handling
    • Password reset tokens

  2. URL Generation

    • Secure link generation
    • One-time use URLs
    • Protected resource access
  3. Form Security
    • CSRF protection
    • Secure form submission
    • State management

API Usage

Best Practices

  1. Storage Selection

    • SQL: For traditional relational database setups
    • File: For simple, single-server deployments
    • MongoDB: For scalable, distributed systems

  2. Token Lifetime

    • Set appropriate token lifetimes based on use case
    • Shorter lifetimes for sensitive operations
    • Consider user experience when setting expiration

  3. Security

    • Always validate tokens before use
    • Use HTTPS for token transmission
    • Implement proper token cleanup
  4. Performance
    • Choose appropriate storage backend for your needs
    • Implement caching where appropriate
    • Clean up expired tokens regularly

Dependencies

Configuration Options

Token Settings

Storage Options

Troubleshooting

Common Issues

  1. Token Validation Failures

    • Check token lifetime settings
    • Verify system time synchronization
    • Ensure proper token storage configuration

  2. Performance Issues

    • Choose appropriate storage backend
    • Implement caching
    • Optimize database queries
    • Consider using MongoDB for high scalability
  3. Security Concerns
    • Verify HTTPS usage
    • Check token generation randomness
    • Monitor token usage patterns
    • Ensure proper file permissions for file storage

Contributing

Contributions to the Horde Token system are welcome. Please follow the Horde contribution guidelines and submit pull requests through GitHub.

License

The Horde Token system is licensed under the same terms as the Horde Framework.

All versions of token with dependencies

PHP Build Version
Package Version
Requires php Version ^7.4 || ^8
horde/exception Version ^3 || dev-FRAMEWORK_6_0
horde/translation Version ^3 || dev-FRAMEWORK_6_0
horde/url Version ^3 || dev-FRAMEWORK_6_0
horde/util Version ^3 || dev-FRAMEWORK_6_0
ext-hash Version *
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package horde/token contains the following files

Loading the files please wait ....