ISSUE-30 Proxy support added for IMS and JWT authentication endpoint #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vivetiwa
force-pushed
the
ISSUE-30-proxy-support-for-ims-jwt-endpoint
branch
from
5b47bbc
to
d74e9eb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Proxy support for IMS and JWT authentication, once proxyHost and proxyPort is provided for AEP inlet endpoint respective IMS or JWT authentication will go through supplied proxy.
Related Issue
#30
Changes
Proxy support for IMS and JWT authentication, once proxyHost and proxyPort is provided for AEP inlet endpoint respective IMS or JWT authentication will go through supplied proxy.
Relevant Documentation
Please enter the links of any docs updated to reflect this change
How Has This Been Tested?
Types of changes
Checklist