-
Notifications
You must be signed in to change notification settings - Fork 158
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
[TT-13186/TT-13275/TT-13331] document upstream basic authentication #5566
base: master
Are you sure you want to change the base?
Conversation
c8718c7
to
d88afef
Compare
✅ PS. Pls add /docs/nightly to the end of url
To edit notification comments on pull requests, go to your Netlify site configuration. |
1 similar comment
✅ PS. Pls add /docs/nightly to the end of url
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ PS. Pls add /docs/nightly to the end of url
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeffy-mathew @sharadregoti we are in a process of consolidating content. Is there another topic this can be part of? maybe upstream mTLS?
|
||
{{< note success >}} | ||
**Note** | ||
`x-tyk-api-gateway.upstream.authentication.enabled` needs to be true to enable upstream authentication. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`x-tyk-api-gateway.upstream.authentication.enabled` needs to be true to enable upstream authentication. | |
`x-tyk-api-gateway.upstream.authentication. basicAuth.enabled` needs to be true to enable upstream authentication. |
Inside your OAS API definition you should configure
x-tyk-api-gateway.upstream.authentication.basicAuth
field.
My understanding is that this field holds a JSON object with 4 values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a prerequisite, x-tyk-api-gateway.upstream.authentication.basicAuth.enabled
is already mentioned.
x-tyk-api-gateway.upstream.authentication.enabled
decides if upstream authentication needs to be performed at all.
|
||
Inside your OAS API definition you should configure `x-tyk-api-gateway.upstream.authentication.basicAuth` field. | ||
- `enabled` needs to be true to enable upstream basic authentication. | ||
- `headerName` is the header to be used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- `headerName` is the header to be used. | |
- `headerName` is the header to be used. Defaults to `Authorization` if not specified. |
|
||
### Via API Definition | ||
|
||
Inside your OAS API definition you should configure `x-tyk-api-gateway.upstream.authentication.basicAuth` field. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inside your OAS API definition you should configure `x-tyk-api-gateway.upstream.authentication.basicAuth` field. | |
In your OAS API definition, configure the `x-tyk-api-gateway.upstream.authentication.basicAuth` field, which is an object containing the following properties: |
@letzya In our new IA, we can include a section on the Authentication & Authorization page to cover this new feature. |
This should not be part of the Client>GW AuthN/AuthZ page. |
Marking it as draft. As @andyo-tyk will use this content to create a new PR. |
For internal users - Please add a Jira DX PR ticket to the subject!
Preview Link
Description
Screenshots (if appropriate)
Checklist
master
.