Skip to content

Authorization with expired token should return different message than authorizing with no token #201

@zelitomas

Description

@zelitomas
$ echo $TOKEN
eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzUxMiJ9.eyJpc3MiOiJsb2NhbGhvc3QiLCJpYXQiOjE2MTMwNjkxMDAsImV4cCI6MTYxMzA3MDkwMCwianRpIjoiNjAyNTdiMmMxOGJlMyIsInN1YiI6ImFkbWluQGEuY3oiLCJnX3VpZCI6MSwiZ19haWQiOjF9.pxTpsYAyygP_bsxvP_70u6SY-IiV4OrUL8BJdBPo1xe8XkmPQBrLTUCXJRsquDzchRX_11vUb0IHj7nQ8FPNpg

$ curl -k -H "Authorization: Bearer ${TOKEN}" -F 'actual_dir=fin' -F 'file[]=@./file1.txt' ${HOST}/api/stor/v1/upload
{
    "api": "core/auth/jwt",
    "version": "1",
    "response_ts": 1613090730,
    "response_id": "6025cfaac9495",
    "status": "Forbidden.",
    "message": "You must be signed in to do this, please provide a valid token.",
    "code": 403
}

Metadata

Metadata

Assignees

Labels

Type

No type
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