Project

General

Profile

Feature #2671

Feature #2666: web client login page improvements

provide a facility to customize the JVM args and Java command line used by the spawner

Added by Greg Shah over 8 years ago. Updated about 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD

History

#1 Updated by Greg Shah over 8 years ago

It can be very useful (for debugging purposes) to customize the JVM args and/or Java command line used by the spawner. We can do this from the directory today. This task is meant to create a facility so that these customizations can be dynamically specified on the login page. We would have to make this secured in some way, such that:

1. They are disabled by default.
2. If enabled, they can be selectively enabled using ACLs and our security environment.

If submitted when they are disallowed, we must ignore any such input and log a warning in the server log. But we should allow the session to still be spawned in such a case, but without the customizations.

#2 Updated by Greg Shah about 8 years ago

I guess the most important feature is to allow specifying the client's command-line bootstrap configuration overrides.

See WebClientBuilder.addClientOptions() where we provide the overrides and WebClientBuilderOptions.readOptions() where we initialize defaults for some overrides.

The standard interactive login page can be updated with an optional field that can be submitted.

The embedded client's launch() API already provides a parameter for this, but it is not honored today.

Also available in: Atom PDF