Skip to content

Separation of errors about authorization vs authentication #2

Description

@mrquincle

Currently trying to obtain a sphere with an incorrect id, for example id 0 leads to 401 errors:

http://crownstone-cloud.herokuapp.com/explorer/#!/Sphere/Sphere_findById

This is exactly the same error as when login doesn't succeed.

It is recommended to use 403 errors for authorization / application logic:

  • See stackoverflow
  • This will also make it easier to see how a connection fails to the cloud.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions