Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P publickey-auth-feathers-nuxt-sockets
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Indienet
  • Spikes
  • Security
  • publickey-auth-feathers-nuxt-sockets
  • Issues
  • #27

Closed
Open
Created Mar 12, 2018 by Aral Balkan@aralOwner

We are passing a non-standard object to auth initialisation in app.js

app.configure(auth({secret: 'secret', service: 'private'}))

According to https://docs.feathersjs.com/api/authentication/server.html#options, secret is not part of the API. Also, why is the service being passed the private service as that, according to the docs, is for “the entity that will be added to the request, socket, and context.params. (ie. req.user, socket.user, context.params.user) service: 'users', // the service to look up the entity”

Assignee
Assign to
Time tracking

Like this? Fund us! Your patronage helps keep us independent and going.