Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Autosubmit API Autosubmit API
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 28
    • Issues 28
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • Autosubmit APIAutosubmit API
  • Issues
  • #59
Closed
Open
Issue created Jan 31, 2024 by Luiggi Tenorio Ku@ltenorioOwner

Manual set of the service param in CAS Authentication

Currently, the authentication module uses the Referer header to build the service param in the CAS protocol. This is an unnecessary security feature as the Referer header is not a reliable source to determine the client host.

Instead, to give more flexibility to the users and support direct authentication with the API without a middle client, the service param can be given directly to the API. This change will not remove the whitelist feature to set the possible clients that can authenticate through the API.

Additionally, a wildcard * can be added to allow any client if desired.

Assignee
Assign to
Time tracking