Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

profiler.rb

  • Sean McGivern's avatar
    f1a7e7fe
    Allow profiler to authenticate by stubbing users directly · f1a7e7fe
    Sean McGivern authored
    Previously, we used a personal access token. This had a couple of
    problems:
    
    1. If the user didn't have a PAT, we couldn't impersonate them.
    2. It depended on reading the raw PAT from the database.
    
    Instead, we can monkey-patch the authentication methods on
    ApplicationController (overriding the Devise ones), and remove them once
    we're done. This does mean that profiles will not profile auth
    correctly, so for that, use a PAT directly.
    f1a7e7fe
    History
    Allow profiler to authenticate by stubbing users directly
    Sean McGivern authored
    Previously, we used a personal access token. This had a couple of
    problems:
    
    1. If the user didn't have a PAT, we couldn't impersonate them.
    2. It depended on reading the raw PAT from the database.
    
    Instead, we can monkey-patch the authentication methods on
    ApplicationController (overriding the Devise ones), and remove them once
    we're done. This does mean that profiles will not profile auth
    correctly, so for that, use a PAT directly.