-
Notifications
You must be signed in to change notification settings - Fork 40
Feature/72 #86
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
Merged
Merged
Feature/72 #86
Changes from 9 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
eabeb87
OAuth2 Implicit Grant call is working again. Token Introspection page…
rcbjBlueMars 45e867f
All functionality working with the OAuth2 Authorization Grant.
rcbjBlueMars db3d5f4
OAuth2 Implicity Grant automated test.
rcbjBlueMars d404362
Docker-based test suite is now working with the OAuth2 Implicit Grant.
rcbjBlueMars af5076a
Added logout test to the OAuth2 Implicit Grant test.
rcbjBlueMars cfdb0be
Updating docker-compose file name for containerized tests. Updated en…
rcbjBlueMars 6fd61ec
Adding repo checkout back into tests pipeline.
rcbjBlueMars 507e368
Added logout step to OAuth2 Authorization Code test.
rcbjBlueMars f3a751f
OIDC Authorization Code Flow (Public Client) test working with token …
rcbjBlueMars c728a88
Refresh Token control and results display now works when you return f…
rcbjBlueMars 972419f
Updated oidc_authorization_code.js test script to make a token refres…
rcbjBlueMars 71e1bd7
Successful local test of oidc_authorization_code.
rcbjBlueMars 2b379ab
Tests that currently work.
rcbjBlueMars d36d8c2
Copy new test files for selelium tests.
rcbjBlueMars File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
Check warning
Code scanning / CodeQL
Information exposure through a stack trace Medium
Copilot Autofix
AI about 1 month ago
To fix the information exposure via stack trace, we should ensure that information sent to the user contains only generic error details, while any detailed error logs (including stack traces) are retained only in server logs. Specifically:
api/server.js, at line 119, replaceres.render('error', { error: e });with a more generic response.log.error, as is already done."An unexpected error occurred."or a structured error object containing a generic message and sanitized code, but never expose stack traces or internal exception details.No change to imports is required; use only standard logging.