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

Fixes when to execute a job using "Remote URL options" #6275 #6276

Merged
merged 2 commits into from Jul 16, 2020
Merged

Conversation

nvalenzuela20
Copy link
Contributor

fixes: #6275

Fix a problem when to execute a job using "Remote URL options" and "Enforcing from allowed values".

solution implemented
Send the "authContext" in the "ExecutionService.addRemoteOptionSelected" method as a parameter because the OptionsUtil.expandUrl method requires the variable usename of the job
and thus don't incorrectly call the OptionsUtil.getHttpSessionInstance () method.

Copy link
Member

@gschueler gschueler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch.

It seems like OptionsUtil.expandUrl falls back to getting the HTTP session for username... I think that should not be done. An enhancement would be to remove that session code and fix all the calls which use that to pass the username explicitly

@jtobard jtobard merged commit e7531d9 into main Jul 16, 2020
@jtobard jtobard deleted the issue/1115 branch July 16, 2020 12:56
gschueler added a commit that referenced this pull request Sep 16, 2020
Fixes when to execute a job using "Remote URL options" #6275 (bp #6276)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Scheduled jobs not running when using Remote URL options and enforcing from allowed values
3 participants