[JBoss JIRA] (JBIDE-19954) Connecting to a server configured for basic auth with Oauth scheme provides no indication
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19954?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19954:
-------------------------------------
Priority: Major (was: Critical)
> Connecting to a server configured for basic auth with Oauth scheme provides no indication
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19954
> URL: https://issues.jboss.org/browse/JBIDE-19954
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Attachments: connection-wiazrd.png
>
>
> # ASSERT: make sure you have an openshift server configured to basic auth (only, no oauth)
> # EXEC: Launch connection wizard, create a new connection, use url of this server in "Server Url" and server type to "OpenShift v3".
> # EXEC: in "Authentication" details pane hit the "retrieve link"
> Result:
> The progress bar shows up for a short time and disappears right afterwards. There's no info in the wizard that tells you why retrieval didnt show up the browser.
> Expected result:
> There's an error that tells you that the local server doesnt support oauth and that you should use basic auth.
> !connection-wiazrd.png!
> It previously worked until we had to alter the 'retrieve' browser to utilize external. This may be resolved if we can re-introduce the original browser dialog
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19954) Connecting to a server configured for basic auth with Oauth scheme provides no indication
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19954?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19954:
-------------------------------------
Attachment: connection-wiazrd.png
> Connecting to a server configured for basic auth with Oauth scheme provides no indication
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19954
> URL: https://issues.jboss.org/browse/JBIDE-19954
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Priority: Critical
> Attachments: connection-wiazrd.png
>
>
> # ASSERT: make sure you have an openshift server configured to basic auth (only, no oauth)
> # EXEC: Launch connection wizard, create a new connection, use url of this server in "Server Url" and server type to "OpenShift v3".
> # EXEC: in "Authentication" details pane hit the "retrieve link"
> Result:
> The progress bar shows up for a short time and disappears right afterwards. There's no info in the wizard that tells you why retrieval didnt show up the browser.
> Expected result:
> There's an error that tells you that the local server doesnt support oauth and that you should use basic auth.
> !connection-wiazrd.png!
> It previously worked until we had to alter the 'retrieve' browser to utilize external. This may be resolved if we can re-introduce the original browser dialog
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19954) Connecting to a server configured for basic auth with Oauth scheme provides no indication
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19954?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19954:
-------------------------------------
Description:
# ASSERT: make sure you have an openshift server configured to basic auth (only, no oauth)
# EXEC: Launch connection wizard, create a new connection, use url of this server in "Server Url" and server type to "OpenShift v3".
# EXEC: in "Authentication" details pane hit the "retrieve link"
Result:
The progress bar shows up for a short time and disappears right afterwards. There's no info in the wizard that tells you why retrieval didnt show up the browser.
Expected result:
There's an error that tells you that the local server doesnt support oauth and that you should use basic auth.
!connection-wiazrd.png!
It previously worked until we had to alter the 'retrieve' browser to utilize external. This may be resolved if we can re-introduce the original browser dialog
was:
Stand-up an openshift server configured to basic auth
Using JBT try to create a connection and retrieve an oauth token
Tooling performs some action but provides no indication that the attempt fails.
It previously worked until we had to alter the 'retrieve' browser to utilize external. This may be resolved if we can re-introduce the original browser dialog
> Connecting to a server configured for basic auth with Oauth scheme provides no indication
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19954
> URL: https://issues.jboss.org/browse/JBIDE-19954
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Priority: Critical
>
> # ASSERT: make sure you have an openshift server configured to basic auth (only, no oauth)
> # EXEC: Launch connection wizard, create a new connection, use url of this server in "Server Url" and server type to "OpenShift v3".
> # EXEC: in "Authentication" details pane hit the "retrieve link"
> Result:
> The progress bar shows up for a short time and disappears right afterwards. There's no info in the wizard that tells you why retrieval didnt show up the browser.
> Expected result:
> There's an error that tells you that the local server doesnt support oauth and that you should use basic auth.
> !connection-wiazrd.png!
> It previously worked until we had to alter the 'retrieve' browser to utilize external. This may be resolved if we can re-introduce the original browser dialog
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19883) purge .cvsignore files from JBT project repos
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19883?page=com.atlassian.jira.plugi... ]
Koen Aers edited comment on JBIDE-19883 at 6/8/15 11:14 AM:
------------------------------------------------------------
Hibernate was also done last week. Unless there are still files trailing that I am not aware of.
https://source.jboss.org/changelog/JBossToolsHibernate?cs=85ae0f091fcab3f...
was (Author: koen.aers):
Hibernate was also done last week. Unless there are still files trailing that I am not aware of.
> purge .cvsignore files from JBT project repos
> ---------------------------------------------
>
> Key: JBIDE-19883
> URL: https://issues.jboss.org/browse/JBIDE-19883
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb, jbpm
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Believe it or not, there are residual .cvsignore files in the jbosstools-* project repos in github. These clearly serve no purpose and should be purged.
> {code}
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.gef/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.projecttemplates/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.xml/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.ext/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.meta.ui/.cvsignore
> ./jbosstools-base/common/features/org.jboss.tools.common.all.test.feature/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.el.core.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.verification.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.model.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.core.test/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.help/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.jdt.ui/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.mapper/.settings/.cvsignore
> ./jbosstools-hibernate/tests/org.hibernate.eclipse.console.test/.settings/.cvsignore
> ./jbosstools-webservices/features/org.jboss.tools.ws.test.feature/.cvsignore
> ./jbosstools-central/maven/features/org.jboss.tools.maven.test.feature/.cvsignore
> ./jbosstools-jbpm/plugins/org.jbpm.gd.jpdl/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui.pages/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.pages.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml.ui/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.pages.xml.test/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.core.test/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml.ui/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.test.feature/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.seam.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.ui/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.verification/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.facelets/.cvsignore
> ./jbosstools-javaee/jsf/features/org.jboss.tools.jsf.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.test/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.verification.test/.cvsignore
> ./jbosstools-server/jmx/features/org.jboss.tools.jmx.test.feature/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.core/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.ui/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.validator/.cvsignore
> ./jbosstools-esb/tests/org.jboss.tools.esb.core.test/.cvsignore
> ./jbosstools-bpel/plugins/org.jboss.tools.bpel.runtimes/.cvsignore
> ./jbosstools-bpel/features/org.jboss.tools.bpel.test.feature/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web.ui/.cvsignore
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19883) purge .cvsignore files from JBT project repos
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19883?page=com.atlassian.jira.plugi... ]
Koen Aers reassigned JBIDE-19883:
---------------------------------
Assignee: Nick Boldt (was: Koen Aers)
Component/s: (was: hibernate)
Hibernate was also done last week. Unless there are still files trailing that I am not aware of.
> purge .cvsignore files from JBT project repos
> ---------------------------------------------
>
> Key: JBIDE-19883
> URL: https://issues.jboss.org/browse/JBIDE-19883
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb, jbpm
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Believe it or not, there are residual .cvsignore files in the jbosstools-* project repos in github. These clearly serve no purpose and should be purged.
> {code}
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification.ui/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.gef/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.model/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.projecttemplates/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.xml/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.text.ext/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.verification/.cvsignore
> ./jbosstools-base/common/plugins/org.jboss.tools.common.meta.ui/.cvsignore
> ./jbosstools-base/common/features/org.jboss.tools.common.all.test.feature/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.el.core.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.verification.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.model.test/.cvsignore
> ./jbosstools-base/common/tests/org.jboss.tools.common.core.test/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.help/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.jdt.ui/.settings/.cvsignore
> ./jbosstools-hibernate/plugins/org.hibernate.eclipse.mapper/.settings/.cvsignore
> ./jbosstools-hibernate/tests/org.hibernate.eclipse.console.test/.settings/.cvsignore
> ./jbosstools-webservices/features/org.jboss.tools.ws.test.feature/.cvsignore
> ./jbosstools-central/maven/features/org.jboss.tools.maven.test.feature/.cvsignore
> ./jbosstools-jbpm/plugins/org.jbpm.gd.jpdl/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui.pages/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.pages.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml/.cvsignore
> ./jbosstools-javaee/seam/plugins/org.jboss.tools.seam.xml.ui/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.pages.xml.test/.cvsignore
> ./jbosstools-javaee/seam/tests/org.jboss.tools.seam.core.test/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml/.cvsignore
> ./jbosstools-javaee/cdi/plugins/org.jboss.tools.cdi.xml.ui/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.test.feature/.cvsignore
> ./jbosstools-javaee/cdi/features/org.jboss.tools.cdi.seam.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.vpe.facelets/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.ui/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.verification/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.richfaces/.cvsignore
> ./jbosstools-javaee/jsf/plugins/org.jboss.tools.jsf.text.ext.facelets/.cvsignore
> ./jbosstools-javaee/jsf/features/org.jboss.tools.jsf.test.feature/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.test/.cvsignore
> ./jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.verification.test/.cvsignore
> ./jbosstools-server/jmx/features/org.jboss.tools.jmx.test.feature/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.core/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.ui/.cvsignore
> ./jbosstools-esb/plugins/org.jboss.tools.esb.validator/.cvsignore
> ./jbosstools-esb/tests/org.jboss.tools.esb.core.test/.cvsignore
> ./jbosstools-bpel/plugins/org.jboss.tools.bpel.runtimes/.cvsignore
> ./jbosstools-bpel/features/org.jboss.tools.bpel.test.feature/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web/.cvsignore
> ./jbosstools-jst/plugins/org.jboss.tools.jst.web.ui/.cvsignore
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19564) Use background job to detect default connection settings
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19564?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19564.
---------------------------------
The detection doesn't really work 100 % yet, but there will be new jiras for that. (Currently I opened this one: JBIDE-19974)
And this JIRA was for making the detection not blocking the UI which seems to work now. So closing this JIRA.
> Use background job to detect default connection settings
> --------------------------------------------------------
>
> Key: JBIDE-19564
> URL: https://issues.jboss.org/browse/JBIDE-19564
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: docker
> Affects Versions: 4.3.0.Alpha1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.0.Beta1
>
>
> In its current form, the New Connection wizard blocks the UI during opening and this can take a few seconds if the default docker deamon is not running (eg: using the REST API). There should be a background job or an immediate opening with a job (and a progress bar) while trying to detect the settings.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19971:
------------------------------------------
I cant reproduce this. I have no such prompt coming up and my import job does not freeze, it is finishing flawlessly.
I have a hard time to understand how you would get a kerberos prompt in the console when importing via JBDS?
[~jcantrill] you mentioned that you were facing unexpected prompts?
[~mlabuda] is this in any way related to JBIDE-12999? Do you have a proxy configured in your JBDS?
> OSE v2 prompts user to enter kerberos credentials from command line while importing an application
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19971
> URL: https://issues.jboss.org/browse/JBIDE-19971
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Blocker
>
> Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) there is hanged importing job in IDE. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there.
> Prompt from CLI looks like:
> Kerberos username [mlabuda]:
> Kerberos password for mlabuda:
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19690) CheckboxTable and the select buttons are not being disabled
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19690?page=com.atlassian.jira.plugi... ]
George Gastaldi commented on JBIDE-19690:
-----------------------------------------
Hi [~psrna],
1) Create an Addon project, choose the ui addon as the single dependency (for speed purposes)
2) Create a command as the following:
{code:java}
import java.lang.annotation.ElementType;
import java.util.concurrent.Callable;
import javax.inject.Inject;
import org.jboss.forge.addon.ui.command.AbstractUICommand;
import org.jboss.forge.addon.ui.context.UIBuilder;
import org.jboss.forge.addon.ui.context.UIExecutionContext;
import org.jboss.forge.addon.ui.input.UIInput;
import org.jboss.forge.addon.ui.input.UIInputMany;
import org.jboss.forge.addon.ui.metadata.WithAttributes;
import org.jboss.forge.addon.ui.result.Result;
import org.jboss.forge.addon.ui.result.Results;
public class ExampleCommand extends AbstractUICommand
{
@Inject
@WithAttributes(label = "Enabled?", defaultValue = "true")
private UIInput<Boolean> enabled;
@Inject
private UIInputMany<ElementType> types;
@Override
public void initializeUI(UIBuilder builder) throws Exception
{
types.setEnabled(new Callable<Boolean>()
{
@Override
public Boolean call() throws Exception
{
return enabled.getValue();
}
});
builder.add(enabled).add(types);
}
@Override
public Result execute(UIExecutionContext context) throws Exception
{
return Results.success();
}
}
{code}
3) Build and install the addon
4) Select the "Example" command and uncheck the "Enabled?" checkbox.
You should see the checkbox table and the select buttons disabled
> CheckboxTable and the select buttons are not being disabled
> ------------------------------------------------------------
>
> Key: JBIDE-19690
> URL: https://issues.jboss.org/browse/JBIDE-19690
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.3.0.Alpha2
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19971:
-------------------------------------
Steps to Reproduce:
ASSERT: Have OSE v2 connection to console.itos.redhat.com with SSH key and domain
EXEC: Open New OpenShift Application wizard and proceed with any application. Hit Finish button to create a new application.
EXEC: Wait till application is created and importing job is started.
RESULT: Command line prompt is shown after some time of running import job for an application.
EXPECTED RESULT: Accept SSH hostkey prompt should be shown and application imported.
was:
ASSERT: Have OSE v2 connection with SSH key and domain
EXEC: Open New OpenShift Application wizard and proceed with any application. Hit Finish button to create a new application.
EXEC: Wait till application is created and importing job is started.
RESULT: Command line prompt is shown after some time of running import job for an application.
EXPECTED RESULT: Accept SSH hostkey prompt should be shown and application imported.
> OSE v2 prompts user to enter kerberos credentials from command line while importing an application
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19971
> URL: https://issues.jboss.org/browse/JBIDE-19971
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Blocker
>
> Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) there is hanged importing job in IDE. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there.
> Prompt from CLI looks like:
> Kerberos username [mlabuda]:
> Kerberos password for mlabuda:
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months