Skip to content

[FEATURE] ACCESS_LOG #448

Closed as not planned
Closed as not planned

Description

@Rycochet

Is your feature request related to a problem? Please describe.

Provide a separate ACCESS_LOG option (default off) that can create a log for which users have logged in, how they logged in (provider), and what time etc.

The full logs give a lot of information about what is going on, but the level of information is very much geared towards finding problems, this is more informative for specific users.

Describe the solution you'd like

An option that can be a single on/off for default logging, and potentially allowing more control over the format and contents for easier security access and analysis.

Describe alternatives you've considered

The alternative is to set the LOG_LEVEL to the minimum level needed, and then cherrypick the relevant information from it, but this can leak internal information about tinyauth that is not relevant to user access.

Additional context

From Google -

AI Overview

There is no single universal "access log standard," but common, predefined formats like the [Combined Log Format(https://www.google.com/search?q=Combined+Log+Format&ie=UTF-&mstk=AUtExfBf7_TGVjSJxf55lGKizYjEuADa8krsLi_ha8oFJJySOlxlezjU8NIZ37kefgYSiM-NLiud8JBblbTuNdALyaBxqPLDg4SuWW1kEztLKrPeudTXnvu3eTB_CjR617R4sv4DxoBV66oBKbGvSY_dOA44SFpGJK2Fcynqzk9N2-QEZlfWgHIexxYKgSPOu9FehLVK0lFz8nv78eS5v8iNRJwv8Q&csui=3&ved=2ahUKEwiExIzc_d2QAxXovokEHeXFAFoQgK4QegQIARAE) are widely used for web servers like NGINX and Apache. These standard formats capture essential request details, including client IP, timestamp, HTTP request, status code, response size, and user agent, which are useful for analysis, monitoring, and troubleshooting. Web servers and proxies also allow administrators to create custom formats to log additional information.

Activity

  1. added this to the v5.0.0 milestone on Nov 23, 2025
  2. github-actions commented on Dec 24, 2025

    @github-actions
    Contributor

    This issue has been inactive for 30 days and will be marked as stale.

  3. steveiliop56 commented on Jan 15, 2026

    @steveiliop56
    Member

    Not really completed, not closing yet.

  4. removed this from the v5.0.0 milestone on Jan 15, 2026
  5. github-actions commented on Feb 15, 2026

    @github-actions
    Contributor

    This issue has been inactive for 30 days and will be marked as stale.

  6. github-actions commented on Mar 18, 2026

    @github-actions
    Contributor

    This issue has been inactive for 30 days and will be marked as stale.

  7. github-actions commented on Mar 26, 2026

    @github-actions
    Contributor

    Closed for inactivity.

  8. steveiliop56 commented on Mar 26, 2026

    @steveiliop56
    Member

    Let's give it some more time.

  9. github-actions commented on Apr 26, 2026

    @github-actions
    Contributor

    This issue has been inactive for 30 days and will be marked as stale.

  10. github-actions commented on May 3, 2026

    @github-actions
    Contributor

    Closed for inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requeststaleThis issue or pull request is stale

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions