Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is security scheme value lowercase or case-insensitive? #1876

Closed
hkosova opened this issue Mar 26, 2019 · 1 comment
Closed

Is security scheme value lowercase or case-insensitive? #1876

hkosova opened this issue Mar 26, 2019 · 1 comment

Comments

@hkosova
Copy link
Contributor

hkosova commented Mar 26, 2019

The scheme field of the Security Scheme Object is defined as follows:

The name of the HTTP Authorization scheme to be used in the Authorization header as defined in RFC7235.

and subsequent examples use scheme: basic and scheme: bearer - with lowercase scheme names.

However, the Authentication Scheme Registry defines the scheme names starting with an uppercase letter:

  • Basic
  • Bearer
  • Digest
  • ...

Could you please clarify if the scheme value must be lowercase, or if both scheme: basic (as in the current examples) and scheme: Basic (as in the Auth Scheme Registry) are valid and equivalent?

@darrelmiller
Copy link
Member

@hkosova As per RFC7235 auth scheme is case insensitive:

2.1. Challenge and Response

HTTP provides a simple challenge-response authentication framework
that can be used by a server to challenge a client request and by a
client to provide authentication information. It uses a case-
insensitive token as a means to identify the authentication scheme,
followed by additional information necessary for achieving

https://tools.ietf.org/html/rfc7235#section-2.1

@hkosova hkosova closed this as completed Apr 1, 2019
char0n added a commit to swagger-api/swagger-js that referenced this issue Jun 18, 2020
As per RFC7235 auth scheme is case insensitive.

2.1. Challenge and Response

HTTP provides a simple challenge-response authentication framework
that can be used by a server to challenge a client request and by a
client to provide authentication information. It uses a case-
insensitive token as a means to identify the authentication scheme,
followed by additional information necessary for achieving.

https://tools.ietf.org/html/rfc7235#section-2.1

Refs #1531, #1473
Refs OAI/OpenAPI-Specification#1876
Refs swagger-api/swagger-ui#5965
char0n added a commit to swagger-api/swagger-js that referenced this issue Jun 18, 2020
As per RFC7235 auth scheme is case insensitive.

2.1. Challenge and Response

HTTP provides a simple challenge-response authentication framework
that can be used by a server to challenge a client request and by a
client to provide authentication information. It uses a case-
insensitive token as a means to identify the authentication scheme,
followed by additional information necessary for achieving.

https://tools.ietf.org/html/rfc7235#section-2.1

Refs #1531, #1473
Refs OAI/OpenAPI-Specification#1876
Refs swagger-api/swagger-ui#5965
char0n added a commit to swagger-api/swagger-js that referenced this issue Jun 18, 2020
As per RFC7235 auth scheme is case insensitive.

2.1. Challenge and Response

HTTP provides a simple challenge-response authentication framework
that can be used by a server to challenge a client request and by a
client to provide authentication information. It uses a case-
insensitive token as a means to identify the authentication scheme,
followed by additional information necessary for achieving.

https://tools.ietf.org/html/rfc7235#section-2.1

Co-authored-by: Helen Kosova <hkosova@users.noreply.github.com>

Refs #1531, #1473
Refs OAI/OpenAPI-Specification#1876
Refs swagger-api/swagger-ui#5965
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants