[JBoss JIRA] (TOOLSDOC-419) Reference to EE6 should refer to EE only
by Len DiMaggio (JIRA)
Len DiMaggio created TOOLSDOC-419:
-------------------------------------
Summary: Reference to EE6 should refer to EE only
Key: TOOLSDOC-419
URL: https://issues.jboss.org/browse/TOOLSDOC-419
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Bug
Components: Installation Guide
Environment: Build Name: 22485, Release Notes 7.1.0-7.1-7.1.0
Build Date: 01-11-2013 17:01:22
Topic ID: 22588-550178 [Latest]
Reporter: Len DiMaggio
Assignee: Michelle Murray
Title: Use Cases of JBoss Developer Studio
Describe the issue:
The reference to EE6:
{quote}
JBoss Developer Studio supports the Java EE 6 specification and provides tools for JAX-RS, Hibernate, and CDI APIs so you can develop the server-side components of your application effortlessly.
{quote}
Should be changed to refer only to "Java EE specification" as JBDS actually supports EE6 for EAP and EE7 for WildFly - it is simpler and less confusing.
Suggestions for improvement:
Additional information:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (TOOLSDOC-418) Awkward wording in section section 1.1
by Len DiMaggio (JIRA)
Len DiMaggio created TOOLSDOC-418:
-------------------------------------
Summary: Awkward wording in section section 1.1
Key: TOOLSDOC-418
URL: https://issues.jboss.org/browse/TOOLSDOC-418
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Bug
Components: Installation Guide
Environment: Build Name: 22485, Release Notes 7.1.0-7.1-7.1.0
Build Date: 01-11-2013 17:01:22
Topic ID: 22589-550126 [Latest]
Reporter: Len DiMaggio
Assignee: Michelle Murray
Priority: Minor
Title: About Red Hat JBoss Developer Studio
Describe the issue:
This is a minor point, but the wording of this section has always seemed awkward:
{quote}
Furthermore, JBoss Developer Studio has many unique features to assist your application development:
Develop new applications using the wizards and project examples of JBoss Central.
Add powerful functionality to applications with minimal effort using Forge Tools.
.
.
{quote}
Suggestions for improvement:
Can we change this to:
{quote}
Furthermore, JBoss Developer Studio has many unique features to assist your application development by enabling you to:
Develop new applications using the wizards and project examples of JBoss Central.
Add powerful functionality to applications with minimal effort using Forge Tools.
{quote}
Additional information:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15847) OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15847?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15847:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have an account in the internal redhat OpenShift Enterprise instance (console.itos.redhat.com) and have it listed in the OpenShift Explorer (NOTICE: this wont happen in a "normal" OSE install that our devs use to hack OSE!)
# EXEC: in the *Web-UI* (or use rhc) create a new application
# EXEC: in *OpenShift Explorer*: select your connection and pick "refresh" from the context menu
Result:
Nothing happens, the new application wont show up
Expected Result:
The new application shows up
was:
# ASSERT: make sure you have an account in the internal redhat OpenShift Enterprise instance (console.itos.redhat.com) and have it listed in the OpenShift Explorer
# EXEC: in the *Web-UI* (or use rhc) create a new application
# EXEC: in *OpenShift Explorer*: select your connection and pick "refresh" from the context menu
Result:
Nothing happens, the new application wont show up
Expected Result:
The new application shows up
> OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
> -------------------------------------------------------------------------
>
> Key: JBIDE-15847
> URL: https://issues.jboss.org/browse/JBIDE-15847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15847) OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15847?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15847:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have an account in the internal redhat OpenShift Enterprise instance (console.itos.redhat.com) and have it listed in the OpenShift Explorer (*NOTICE*: this wont happen in a "normal" OSE install that our devs use to hack OSE! This is only happening in our internal RH OSE instance which is using LDAP/Kerberos)
# EXEC: in the *Web-UI* (or use rhc) create a new application
# EXEC: in *OpenShift Explorer*: select your connection and pick "refresh" from the context menu
Result:
Nothing happens, the new application wont show up
Expected Result:
The new application shows up
was:
# ASSERT: make sure you have an account in the internal redhat OpenShift Enterprise instance (console.itos.redhat.com) and have it listed in the OpenShift Explorer (NOTICE: this wont happen in a "normal" OSE install that our devs use to hack OSE!)
# EXEC: in the *Web-UI* (or use rhc) create a new application
# EXEC: in *OpenShift Explorer*: select your connection and pick "refresh" from the context menu
Result:
Nothing happens, the new application wont show up
Expected Result:
The new application shows up
> OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
> -------------------------------------------------------------------------
>
> Key: JBIDE-15847
> URL: https://issues.jboss.org/browse/JBIDE-15847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2806) JBDS crashed after Help > Check for updates :: 7.0.0.GA (B364) -> 7.0.1.GA on OSX 10.8.5 (Mountain Lion)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2806?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2806:
-------------------------------------------
I just noticed the stack trace states '/*/' in some of its listed paths.
Is that * actually on the file system ?
> JBDS crashed after Help > Check for updates :: 7.0.0.GA (B364) -> 7.0.1.GA on OSX 10.8.5 (Mountain Lion)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2806
> URL: https://issues.jboss.org/browse/JBDS-2806
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 7.0.0.GA, 7.0.1.GA
> Environment: Mac OS
> Reporter: Oleg Lovkis
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 7.1.0.CR1
>
> Attachments: JBDS2806.crashdump.txt
>
>
> On OSX 10.8.5 (Mountain Lion) with Oracle JDK 1.7u25 x64, update from JBDS 7.0.0.GA (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) to 7.0.1.GA caused crash after performing Help -> Check For Updates
> See [^JBDS2806.crashdump.txt] for complete dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15847) OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15847?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15847 at 11/4/13 8:05 AM:
-------------------------------------------------------------------
The reason for this to happen is a "rename" of the user in OSE due to using LPDAP/Kerberos. I create the connection using *<redhat-user>*. The user being stored in OSE is "renamed", "automcompleted". When querying OSE for the user of the domain I get *<redhat-user(a)redhat.com>*.
According to Brenton Leanhardt this is due to a misconfigured backend. The user-rewrite happens because OSE is not configured using *KrbLocalUserMapping On*
{quote}
01:43:53 PM) adietish: bleanhar: ok. in your appreciation, do you think that this is unique to our setup or may this happen for customers?
(01:43:56 PM) bleanhar: it's sort of a mess to rename users so I'm betting they never added it after we learned about this
(01:44:24 PM) bleanhar: adietish: it's sort of an edge case. I would _highly_ recommend customers use 'KrbLocalUserMapping On' in their environments
(01:44:28 PM) bleanhar: it's now the default
(01:44:33 PM) adietish: bleanhar: ok, gotcha, so if I read you right the user-renaming can be avoided via this config?
(01:45:55 PM) bleanhar: adietish: correct, this problem can (and should be) avoided
(01:45:59 PM) bleanhar: I'll follow up with IT
{quote}
was (Author: adietish):
The reason for this to happen is a "rename" of the user in OSE due to using LPDAP/Kerberos. I create the connection using *<redhat-user>*. The user being stored in OSE is "renamed", "automcompleted". When querying OSE for the user of the domain I get *<redhat-user(a)redhat.com>*.
According to Brenton Leanhardt this is due to a misconfigured backend. The user-rewrite happens because OSE is not configured using *KrbLocalUserMapping On*
{quote}
01:43:53 PM) adietish: bleanhar: ok. in your appreciation, do you think that this is unique to our setup or may this happen for customers?
(01:43:56 PM) bleanhar: it's sort of a mess to rename users so I'm betting they never added it after we learned about this
(01:44:24 PM) bleanhar: adietish: it's sort of an edge case. I would _highly_ recommend customers use 'KrbLocalUserMapping On' in their environments
(01:44:28 PM) bleanhar: it's now the default
(01:44:33 PM) adietish: bleanhar: ok, gotcha, so if I read you right the user-renaming can be avoided via this config?
(01:45:55 PM) bleanhar: adietish: correct, this problem can (and should be) avoided
{quote}
> OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
> -------------------------------------------------------------------------
>
> Key: JBIDE-15847
> URL: https://issues.jboss.org/browse/JBIDE-15847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15847) OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15847?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15847:
------------------------------------------
The reason for this to happen is a "rename" of the user in OSE due to using LPDAP/Kerberos. I create the connection using *<redhat-user>*. The user being stored in OSE is "renamed", "automcompleted". When querying OSE for the user of the domain I get *<redhat-user(a)redhat.com>*.
According to Brenton Leanhardt this is due to a misconfigured backend. The user-rewrite happens because OSE is not configured using *KrbLocalUserMapping On*
{quote}
01:43:53 PM) adietish: bleanhar: ok. in your appreciation, do you think that this is unique to our setup or may this happen for customers?
(01:43:56 PM) bleanhar: it's sort of a mess to rename users so I'm betting they never added it after we learned about this
(01:44:24 PM) bleanhar: adietish: it's sort of an edge case. I would _highly_ recommend customers use 'KrbLocalUserMapping On' in their environments
(01:44:28 PM) bleanhar: it's now the default
(01:44:33 PM) adietish: bleanhar: ok, gotcha, so if I read you right the user-renaming can be avoided via this config?
(01:45:55 PM) bleanhar: adietish: correct, this problem can (and should be) avoided
{quote}
> OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
> -------------------------------------------------------------------------
>
> Key: JBIDE-15847
> URL: https://issues.jboss.org/browse/JBIDE-15847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2806) JBDS crashed after Help > Check for updates :: 7.0.0.GA (B364) -> 7.0.1.GA on OSX 10.8.5 (Mountain Lion)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2806?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2806:
--------------------------------------
Fix Version/s: 7.1.0.CR1
> JBDS crashed after Help > Check for updates :: 7.0.0.GA (B364) -> 7.0.1.GA on OSX 10.8.5 (Mountain Lion)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2806
> URL: https://issues.jboss.org/browse/JBDS-2806
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 7.0.0.GA, 7.0.1.GA
> Environment: Mac OS
> Reporter: Oleg Lovkis
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 7.1.0.CR1
>
> Attachments: JBDS2806.crashdump.txt
>
>
> On OSX 10.8.5 (Mountain Lion) with Oracle JDK 1.7u25 x64, update from JBDS 7.0.0.GA (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) to 7.0.1.GA caused crash after performing Help -> Check For Updates
> See [^JBDS2806.crashdump.txt] for complete dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15830) openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
by Brenton Leanhardt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ]
Brenton Leanhardt commented on JBIDE-15830:
-------------------------------------------
I debugged this using wireshark. With openshift-java-client 2.3.0.Final I saw the user-agent set correctly as well as the authkey passed in correctly. With all later versions I saw the authkey was correct but the user-agent was the JVM version. I verified that authkey passed up by the later versions of openshift-java-client was correct and that it could be decrypted properly.
> openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15830
> URL: https://issues.jboss.org/browse/JBIDE-15830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Brenton Leanhardt
> Assignee: Andre Dietisheim
> Labels: openshift-java-client
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin.
> In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling.
> You can see this for details:
> https://github.com/openshift/origin-server/blob/master/documentation/arch...
> In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15847) OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15847?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15847:
-------------------------------------
Summary: OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect (was: OpenShift Enterprise: Refreshing domain has no effect)
Steps to Reproduce:
# ASSERT: make sure you have an account in the internal redhat OpenShift Enterprise instance (console.itos.redhat.com) and have it listed in the OpenShift Explorer
# EXEC: in the *Web-UI* (or use rhc) create a new application
# EXEC: in *OpenShift Explorer*: select your connection and pick "refresh" from the context menu
Result:
Nothing happens, the new application wont show up
Expected Result:
The new application shows up
Workaround Description: Remove your connection in OpenShift Explorer and re-create it.
> OpenShift Explorer: OpenShift Enterprise: Refreshing domain has no effect
> -------------------------------------------------------------------------
>
> Key: JBIDE-15847
> URL: https://issues.jboss.org/browse/JBIDE-15847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months