Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
lemonldap-ng
lemonldap-ng
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 260
    • Issues 260
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LemonLDAP NG
  • lemonldap-nglemonldap-ng
  • Issues
  • #1591

Closed
Open
Opened Dec 17, 2018 by Clément OUDOT@clement_oudotOwner

$req->user not available in plugins authenticated routes

When creating a plugin that add an authroute:

sub init {
          my ($self) = @_;
          $self->addAuthRoute( addLinkedIn => 'linkedin', [ 'GET' ] );
          return 1;
}

We can't find user main identifier in $req->user:

sub linkedin {
          my ($self, $req) = @_;

          my $userid = $req->user;

          $self->p->logger->debug("Associate LinkedIn account for $userid");

          return PE_OK;
}

But we have $req->userData. We should maybe always provide $req->user to have consistent code in plugins.

Assignee
Assign to
2.0.1
Milestone
2.0.1 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: lemonldap-ng/lemonldap-ng#1591