Skip to content

bug: OPTIONS Hitting Authentication #40

@ProgrammingByPermutation

Description

The logs have all these "Bearer was not authenticated. Failure message: No token" messages. Some of these are a result of the HTTP OPTIONS being sent to the server for CORS. We really don't want CORS getting auth checked.

This usually happens because either:

  1. Two components in the DI are incompatible and one is trampling on another.
  2. The DI are in the wrong order (calling UseCors too early or too late)

Not sure its even solvable and it doesn't hurt anything, currently.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions