[JBoss JIRA] Created: (AS7-1053) Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface
1:11 p.m.
Revisit requirement that realm name needs to match endpoint name with Remoting / Native
Interface
-------------------------------------------------------------------------------------------------
Key: AS7-1053
URL: https://issues.jboss.org/browse/AS7-1053
Project: Application Server 7
Issue Type: Task
Components: Remoting
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Alpha1
It is reported that the realm used for the endpoint needs to match the endpoint name - for
this reason the realm appears as 'endpoint'
The realm should actually match the name of the realm being used as this is to inform the
user of the realm they are using. This may also need expanding to multiple realms in the
future so users in different realms can all authenticate against the same resource.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:29 a.m.
New subject: [JBoss JIRA] Updated: (AS7-1053) Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface
[
https://issues.jboss.org/browse/AS7-1053?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-1053:
----------------------------------
Fix Version/s: 7.1.0.Beta1
(was: 7.1.0.Alpha1)
Revisit requirement that realm name needs to match endpoint name with
Remoting / Native Interface
-------------------------------------------------------------------------------------------------
Key: AS7-1053
URL: https://issues.jboss.org/browse/AS7-1053
Project: Application Server 7
Issue Type: Task
Components: Remoting
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Beta1
It is reported that the realm used for the endpoint needs to match the endpoint name -
for this reason the realm appears as 'endpoint'
The realm should actually match the name of the realm being used as this is to inform the
user of the realm they are using. This may also need expanding to multiple realms in the
future so users in different realms can all authenticate against the same resource.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:49 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1053) Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface
[
https://issues.jboss.org/browse/AS7-1053?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-1053:
----------------------------------
Fix Version/s: 7.0.2.Final
(was: 7.1.0.Beta1)
Revisit requirement that realm name needs to match endpoint name with
Remoting / Native Interface
-------------------------------------------------------------------------------------------------
Key: AS7-1053
URL: https://issues.jboss.org/browse/AS7-1053
Project: Application Server 7
Issue Type: Task
Components: Remoting
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.0.2.Final
It is reported that the realm used for the endpoint needs to match the endpoint name -
for this reason the realm appears as 'endpoint'
The realm should actually match the name of the realm being used as this is to inform the
user of the realm they are using. This may also need expanding to multiple realms in the
future so users in different realms can all authenticate against the same resource.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:56 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1053) Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface
[
https://issues.jboss.org/browse/AS7-1053?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-1053:
----------------------------------
Description:
It is reported that the realm used for the endpoint needs to match the endpoint name - for
this reason the realm appears as 'endpoint'
The realm should actually match the name of the realm being used as this is to inform the
user of the realm they are using. This may also need expanding to multiple realms in the
future so users in different realms can all authenticate against the same resource.
XNIO-96 provides a mechanism for non-standard (yet supported by the Provider) options to
be specified - provided that fix is accepted the name of the realm can be passed in the
OptionsMap - just first ensure all spaces are removed / replaced from the realm name as
this is used as the delimiter.
was:
It is reported that the realm used for the endpoint needs to match the endpoint name - for
this reason the realm appears as 'endpoint'
The realm should actually match the name of the realm being used as this is to inform the
user of the realm they are using. This may also need expanding to multiple realms in the
future so users in different realms can all authenticate against the same resource.
Revisit requirement that realm name needs to match endpoint name with
Remoting / Native Interface
-------------------------------------------------------------------------------------------------
Key: AS7-1053
URL: https://issues.jboss.org/browse/AS7-1053
Project: Application Server 7
Issue Type: Task
Components: Remoting
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.0.2.Final
It is reported that the realm used for the endpoint needs to match the endpoint name -
for this reason the realm appears as 'endpoint'
The realm should actually match the name of the realm being used as this is to inform the
user of the realm they are using. This may also need expanding to multiple realms in the
future so users in different realms can all authenticate against the same resource.
XNIO-96 provides a mechanism for non-standard (yet supported by the Provider) options to
be specified - provided that fix is accepted the name of the realm can be passed in the
OptionsMap - just first ensure all spaces are removed / replaced from the realm name as
this is used as the delimiter.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:56 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1053) Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface
[
https://issues.jboss.org/browse/AS7-1053?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-1053:
----------------------------------
Component/s: Domain Management
Security
Revisit requirement that realm name needs to match endpoint name with
Remoting / Native Interface
-------------------------------------------------------------------------------------------------
Key: AS7-1053
URL: https://issues.jboss.org/browse/AS7-1053
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Remoting, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.0.2.Final
It is reported that the realm used for the endpoint needs to match the endpoint name -
for this reason the realm appears as 'endpoint'
The realm should actually match the name of the realm being used as this is to inform the
user of the realm they are using. This may also need expanding to multiple realms in the
future so users in different realms can all authenticate against the same resource.
XNIO-96 provides a mechanism for non-standard (yet supported by the Provider) options to
be specified - provided that fix is accepted the name of the realm can be passed in the
OptionsMap - just first ensure all spaces are removed / replaced from the realm name as
this is used as the delimiter.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:33 a.m.
New subject: [JBoss JIRA] Updated: (AS7-1053) Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface
[
https://issues.jboss.org/browse/AS7-1053?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-1053:
----------------------------------
Priority: Critical (was: Major)
Fix Version/s: 7.1.0.Beta1
(was: 7.0.2.Final)
Revisit requirement that realm name needs to match endpoint name with
Remoting / Native Interface
-------------------------------------------------------------------------------------------------
Key: AS7-1053
URL: https://issues.jboss.org/browse/AS7-1053
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Remoting, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 7.1.0.Beta1
It is reported that the realm used for the endpoint needs to match the endpoint name -
for this reason the realm appears as 'endpoint'
The realm should actually match the name of the realm being used as this is to inform the
user of the realm they are using. This may also need expanding to multiple realms in the
future so users in different realms can all authenticate against the same resource.
XNIO-96 provides a mechanism for non-standard (yet supported by the Provider) options to
be specified - provided that fix is accepted the name of the realm can be passed in the
OptionsMap - just first ensure all spaces are removed / replaced from the realm name as
this is used as the delimiter.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:37 a.m.
New subject: [JBoss JIRA] (AS7-1053) Revisit requirement that realm name needs to match endpoint name with Remoting / Native Interface
[
https://issues.jboss.org/browse/AS7-1053?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse resolved AS7-1053.
-----------------------------------
Resolution: Done
https://github.com/jbossas/jboss-as/commit/4d344c709b2cb4aa798f1353cc40bb...
Revisit requirement that realm name needs to match endpoint name with
Remoting / Native Interface
-------------------------------------------------------------------------------------------------
Key: AS7-1053
URL: https://issues.jboss.org/browse/AS7-1053
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Remoting, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 7.1.0.Beta1
It is reported that the realm used for the endpoint needs to match the endpoint name -
for this reason the realm appears as 'endpoint'
The realm should actually match the name of the realm being used as this is to inform the
user of the realm they are using. This may also need expanding to multiple realms in the
future so users in different realms can all authenticate against the same resource.
XNIO-96 provides a mechanism for non-standard (yet supported by the Provider) options to
be specified - provided that fix is accepted the name of the realm can be passed in the
OptionsMap - just first ensure all spaces are removed / replaced from the realm name as
this is used as the delimiter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4756
days inactive
4891
days old
6 comments
2 participants
participants (2)
-
Darran Lofthouse (JIRA) -
Darran Lofthouse (Resolved) (JIRA)