]
Denis Golovin updated JBDS-3627:
--------------------------------
Sprint: (was: devex #119 August 2016)
Installer needs to help move past lack of t/c signing
-----------------------------------------------------
Key: JBDS-3627
URL:
https://issues.jboss.org/browse/JBDS-3627
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Enhancement
Components: platform-installer
Reporter: Joshua Wilson
Assignee: Denis Golovin
Labels: havoc
Fix For: 10.1.0.GA
Attachments: Installer-not-signed-tc.PNG
DevSuite installer uses "REST services in JBoss Download Manager" explained
here
https://mojo.redhat.com/docs/DOC-940689.
DevSuite Intsaller follows the explanation for tc-accepted entry point [code is
here|https://github.com/redhat-developer-tooling/developer-platform-insta...].
It uses file from previous CDK release (published in cdn and available through download
manager) to do verification:
1. that provided credentials are valid;
2. that required T&C's are signed.
There are two major use cases for developers installing DevSuite using Installer:
1. Direct download - when developer sign in to
developers.redhat.com and download
installer himeslf;
2. Shared installer - when someone share installer with developers without account.
There two kind of users involved in those scenarios above:
1. New users that must go through registration process;
2. Registered users.
*Direct download*
For new ones registration process is really simple now. After creating RHD account and
downloading installer there is no additional steps to get through installation.
For already registered users there could be problems related to T&C's and
authentication reported here
https://issues.jboss.org/browse/RHDENG-579.
So far there are two kind of problems:
1. Users can login and download DevSuite installer, but cannot use the same credentials
to install;
2. Users that can login in to
developers.redhat.com and get request to sign additional
T&C's but credentials for the same user in DevSuite Installer reported as invalid
when REST tc-accepted entry point is used
*Shared Download*
In this scenario new users without account can press Register link, then go through
registration process in browser return back to installer and use new account credentials
for installation.
Registered users could need to sign additional T&C's if missing and would be good
to show external link to do so. Current entry point tc-accepted does not provide any hints
where missing T&C's could be signed.