August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3983) DevSuite Installer proxy support

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3983: ----------------------------- > DevSuite Installer proxy support > -------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM2 > > > DevSuite installer cannot verify user credentials and T&C's when running in corporate network behind proxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3983) DevSuite Installer proxy support

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3983: -------------------------------- Fix Version/s: 10.1.0.AM2 > DevSuite Installer proxy support > -------------------------------- > > Key: JBDS-3983 > URL: https://issues.jboss.org/browse/JBDS-3983 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM2 > > > DevSuite installer cannot verify user credentials and T&C's when running in corporate network behind proxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22867) JBT could not get projects created by openshift cli tool

by Peng Li (JIRA)

Peng Li created JBIDE-22867: ------------------------------- Summary: JBT could not get projects created by openshift cli tool Key: JBIDE-22867 URL: https://issues.jboss.org/browse/JBIDE-22867 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.x Environment: JBoss OpenShift 3 Tools 3.3.0.v20160721-2201 openshift v3.3.0.12 kubernetes v1.3.0+57fb9ac etcd 2.3.0+git Reporter: Peng Li User could not get projects created by oc command -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-3627 at 8/1/16 9:15 PM: ------------------------------------------------------------- [~dhladky]The screenshot above is from DevSuite Installer. It is first page in installer which accepts Red Hat Account Credentials. I also updated description and I hope it helps to understand what kind of usability problems we have in DevSuite Installer Major usability problem is when "Terms and Conditions for CDK have not been signed." error shown because tc-accepted request returns Status 200 and false. Would be good to get url with missing T&C's check boxes without triggering download for specific file. https://developers.redhat.com/download-manager/link/<someid> approach to pass T&C's signing without download triggered. Seems to work for devstudio product code only. cdk returns "Not Found" page. was (Author: dgolovin): [~dhladky]The screenshot above is from DevSuite Installer. It is first page in installer which accepts Red Hat Account Credentials. I also updated description and I hope it helps to understand what kind of usability problems we have in DevSuite Installer Major usability problem is when "Terms and Conditions for CDK have not been signed." error shown because tc-accepted request returns Status 200 and false. Would be good to get url with missing T&C's check boxes without triggering download for specific file. > 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.AM3 > > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3627: ------------------------------------- [~dhladky]The screenshot above is from DevSuite Installer. It is first page in installer which accepts Red Hat Account Credentials. I also updated description and I hope it helps to understand what kind of usability problems we have in DevSuite Installer Major usability problem is when "Terms and Conditions for CDK have not been signed." error shown because tc-accepted request returns Status 200 and false. Would be good to get url with missing T&C's check boxes without triggering download for specific file. > 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.AM3 > > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- Description: 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. was: When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it. > 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.AM3 > > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- > 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.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- > 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.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3627: -------------------------------- > 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.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3627: ----------------------------- > 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.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2016