June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19905) Connection token and authentication scheme are not saved

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19905?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19905: ------------------------------------- Attachment: after-refresh-no-token.png after-refresh-no-username-pw.png edit-after-username-pw-provided.png > Connection token and authentication scheme are not saved > -------------------------------------------------------- > > Key: JBIDE-19905 > URL: https://issues.jboss.org/browse/JBIDE-19905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: after-refresh-no-token.png, after-refresh-no-username-pw.png, edit-after-username-pw-provided.png, unauthorized.png > > > Fix saving of a user's token and the auth scheme for a server. Might consider setting the username for a connection to user.getName() instead of user.getFullName() -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19905) Connection token and authentication scheme are not saved

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19905?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19905: ------------------------------------------ If I now refresh the connection, the connection dialog pops up empty, no OAuth token nor username/password are filled-in: !after-refresh-no-token.png! !after-refresh-no-username-pw.png! # EXEC: switch to "Basic" and fill in username and password Result: Connection now authenticates successfully, the resources are loaded. # EXE: Edit your connection Result: Now the token is filled-in. OK !edit-after-username-pw-provided.png! > Connection token and authentication scheme are not saved > -------------------------------------------------------- > > Key: JBIDE-19905 > URL: https://issues.jboss.org/browse/JBIDE-19905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: after-refresh-no-token.png, after-refresh-no-username-pw.png, edit-after-username-pw-provided.png, unauthorized.png > > > Fix saving of a user's token and the auth scheme for a server. Might consider setting the username for a connection to user.getName() instead of user.getFullName() -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3384: ----------------------------------- Lars hasn't been able to investigate this with me yet, since he's lacking a target platform for Mars with the updates to tm needed. The word through the grapevine is that the TP will be coming *after* our Beta1 release. Is this correct [~lhein] and [~pleacu]? I'll push this to beta2 for now. > Investigate how the terminal changes in Mars will/should affect us > ------------------------------------------------------------------- > > Key: JBDS-3384 > URL: https://issues.jboss.org/browse/JBDS-3384 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, forge, openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Terminal (console) support in eclipse mars is changing and we should > make sure we adjust for it. > Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html > Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now. > This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new. > As we find what it entails we should link those issues to this jira. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17686: -------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17686: ------------------------------------- I'm pushing this for now while we wait to see if upstream has any solution to https://bugs.eclipse.org/bugs/show_bug.cgi?id=468875 > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19927) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Arquillian]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19927?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-19927. --------------------------------- Resolution: Done > For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Arquillian] > -------------------------------------------------------- > > Key: JBIDE-19927 > URL: https://issues.jboss.org/browse/JBIDE-19927 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Beta1 [Arquillian]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta1x > git push origin jbosstools-4.3.0.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and > * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19905) Connection token and authentication scheme are not saved

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19905?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19905 at 6/3/15 5:49 PM: ------------------------------------------------------------------ with the patch I now have the following when using basic auth: # ASSERT: make sure that you have a connection in explorer that's using username & password and password stored to secure storage # EXEC: restart Eclipse # EXEC in explorer unfold your connection # ASSERT: SSL connection dialog pops up # EXEC: confirm it Result: An error dialog pops up telling me that my connection is unauthorized !unauthorized.png! in the Eclipse log I see the following {code} com.openshift.internal.restclient.http.UnauthorizedException: Unauthorized at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:208) at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:151) at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:130) at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:92) at com.openshift.internal.restclient.DefaultClient.getVersion(DefaultClient.java:307) at com.openshift.internal.restclient.DefaultClient.getOpenShiftVersions(DefaultClient.java:283) at com.openshift.internal.restclient.DefaultClient.getOpenShiftAPIVersion(DefaultClient.java:297) at com.openshift.internal.restclient.DefaultClient.getTypeMappings(DefaultClient.java:332) at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:119) at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:113) at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:108) at org.jboss.tools.openshift.core.connection.Connection.get(Connection.java:309) at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:57) at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:124) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://localhost:8443/osapi at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1839) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:147) ... 13 more {code} [~jcantrill] Is this expected, a different bug? was (Author: adietish): with the patch I now have the following when using basic auth: # ASSERT: make sure that you have a connection in explorer that's using username & password and password stored to secure storage # EXEC: restart Eclipse # EXEC in explorer unfold your connection # ASSERT: SSL connection dialog pops up # EXEC: confirm it Result: An error dialog pops up telling me that my connection is unauthorized !unauthorized.png! [~jcantrill] Is this expected, a different bug? > Connection token and authentication scheme are not saved > -------------------------------------------------------- > > Key: JBIDE-19905 > URL: https://issues.jboss.org/browse/JBIDE-19905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: unauthorized.png > > > Fix saving of a user's token and the auth scheme for a server. Might consider setting the username for a connection to user.getName() instead of user.getFullName() -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19905) Connection token and authentication scheme are not saved

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19905?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19905 at 6/3/15 5:45 PM: ------------------------------------------------------------------ with the patch I now have the following when using basic auth: # ASSERT: make sure that you have a connection in explorer that's using username & password and password stored to secure storage # EXEC: restart Eclipse # EXEC in explorer unfold your connection # ASSERT: SSL connection dialog pops up # EXEC: confirm it Result: An error dialog pops up telling me that my connection is unauthorized !unauthorized.png! [~jcantrill] Is this expected, a different bug? was (Author: adietish): with the patch I now have the following when using basic auth: # ASSERT: make sure that you have a connection in explorer that's using username & password and password stored to secure storage # EXEC: restart Eclipse # EXEC in explorer unfold your connection # ASSERT: SSL connection dialog pops up # EXEC: confirm it Result: An error dialog pops up telling me that my connection is unauthorized !unauthorized.png! > Connection token and authentication scheme are not saved > -------------------------------------------------------- > > Key: JBIDE-19905 > URL: https://issues.jboss.org/browse/JBIDE-19905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: unauthorized.png > > > Fix saving of a user's token and the auth scheme for a server. Might consider setting the username for a connection to user.getName() instead of user.getFullName() -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19905) Connection token and authentication scheme are not saved

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19905?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19905: ------------------------------------- Attachment: unauthorized.png > Connection token and authentication scheme are not saved > -------------------------------------------------------- > > Key: JBIDE-19905 > URL: https://issues.jboss.org/browse/JBIDE-19905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: unauthorized.png > > > Fix saving of a user's token and the auth scheme for a server. Might consider setting the username for a connection to user.getName() instead of user.getFullName() -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19905) Connection token and authentication scheme are not saved

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19905?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19905: ------------------------------------------ with the patch I now have the following when using basic auth: # ASSERT: make sure that you have a connection in explorer that's using username & password and password stored to secure storage # EXEC: restart Eclipse # EXEC in explorer unfold your connection # ASSERT: SSL connection dialog pops up # EXEC: confirm it Result: An error dialog pops up telling me that my connection is unauthorized !unauthorized.png! > Connection token and authentication scheme are not saved > -------------------------------------------------------- > > Key: JBIDE-19905 > URL: https://issues.jboss.org/browse/JBIDE-19905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: unauthorized.png > > > Fix saving of a user's token and the auth scheme for a server. Might consider setting the username for a connection to user.getName() instead of user.getFullName() -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015