Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • lemonldap-ng lemonldap-ng
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 327
    • Issues 327
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LemonLDAP NGLemonLDAP NG
  • lemonldap-nglemonldap-ng
  • Issues
  • #2244
Closed
Open
Issue created Jun 18, 2020 by Clément OUDOT@clement_oudotOwner

Use configuration key in user log messages for all Issuer modules

We display some logs when a user is allowed to access a CAS/SAML/OIDC application, but we don't use the same attribute to identify the application:

  • With CAS: the service URL
  • With SAML: the SP entityID
  • With OIDC: the RP configuration key

I think it would be better to use the configuration key, whatever the protocol is. It could have an impact for people parsing log messages, but I would like to add this in %2.0.9 with an upgrade note.

We should also add a log in Issuer get code.

Assignee
Assign to
Time tracking