[JBoss JIRA] (WFCORE-4166) HttpListenerRegistryService is not exposed via a capability
by Brian Stansberry (Jira)
Brian Stansberry created WFCORE-4166:
----------------------------------------
Summary: HttpListenerRegistryService is not exposed via a capability
Key: WFCORE-4166
URL: https://issues.jboss.org/browse/WFCORE-4166
Project: WildFly Core
Issue Type: Bug
Components: Management, Remoting
Reporter: Brian Stansberry
Assignee: Yeray Borges
HttpListenerRegistryService.SERVICE_NAME should be deprecated and the remoting subsystem should add a RuntimeCapability the exposes ListenerRegistry. The HttpListenerRegistryService should then be exposed under that capability's ServiceName, with an alias added for the legacy HttpListenerRegistryService.SERVICE_NAME.
This will help eliminate a hard dependency on the org.jboss.as.remoting module from the messaging subsystem in full.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3109) [DMN Designer] Add additional Properties to drill-down
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3109?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3109:
-----------------------------------
Description:
The Properties Panel currently shows properties for Stunner-level "graph" components.
*Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Literal expression
||Selected item||Properties panel items||type|| ||
|Cell|ExpressionLanguage|URI|(/)|
h3. Context
||Selected item||Properties panel items||type|| ||
|Row|type Ref|ItemDefinition ref (same which applies to Key Cell|(/)|
|Column|n/a|n/a|n/a|
|Key Cell|type Ref|ItemDefinition ref|(/)|
|Value Cell|ExpressionLanguage|URI|(/)|
h3. Decision Table
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
| Input Column|Constraints|Text field|
|Output Column|Output values|Unary tests|
|Output Column|Default Output|expression|
|Cell|ExpressionLanguage|URI|
h3. Relation
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|type Ref|ItemDefinition ref|
|Cell|ExpressionLanguage|URI|
h3. Function
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|n/a|n/a|
|Cell|ExpressionLanguage|URI|
h3. Invocation
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|n/a|n/a|
|Cell|ExpressionLanguage|URI|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
was:
The Properties Panel currently shows properties for Stunner-level "graph" components.
*Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Literal expression
||Selected item||Properties panel items||type|| ||
|Cell|ExpressionLanguage|URI|(/)|
h3. Context
||Selected item||Properties panel items||type||
|Row|type Ref|ItemDefinition ref (same which applies to Key Cell|
|Column|n/a|n/a|
|Key Cell|type Ref|ItemDefinition ref|
|Value Cell|ExpressionLanguage|URI|
h3. Decision Table
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
| Input Column|Constraints|Text field|
|Output Column|Output values|Unary tests|
|Output Column|Default Output|expression|
|Cell|ExpressionLanguage|URI|
h3. Relation
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|type Ref|ItemDefinition ref|
|Cell|ExpressionLanguage|URI|
h3. Function
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|n/a|n/a|
|Cell|ExpressionLanguage|URI|
h3. Invocation
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|n/a|n/a|
|Cell|ExpressionLanguage|URI|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
> [DMN Designer] Add additional Properties to drill-down
> ------------------------------------------------------
>
> Key: DROOLS-3109
> URL: https://issues.jboss.org/browse/DROOLS-3109
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The Properties Panel currently shows properties for Stunner-level "graph" components.
> *Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
> h2. Properties on the Grid Level
> The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
> (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
> h3. Literal expression
> ||Selected item||Properties panel items||type|| ||
> |Cell|ExpressionLanguage|URI|(/)|
> h3. Context
> ||Selected item||Properties panel items||type|| ||
> |Row|type Ref|ItemDefinition ref (same which applies to Key Cell|(/)|
> |Column|n/a|n/a|n/a|
> |Key Cell|type Ref|ItemDefinition ref|(/)|
> |Value Cell|ExpressionLanguage|URI|(/)|
> h3. Decision Table
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> | Input Column|Constraints|Text field|
> |Output Column|Output values|Unary tests|
> |Output Column|Default Output|expression|
> |Cell|ExpressionLanguage|URI|
> h3. Relation
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> |Column|type Ref|ItemDefinition ref|
> |Cell|ExpressionLanguage|URI|
> h3. Function
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> |Column|n/a|n/a|
> |Cell|ExpressionLanguage|URI|
> h3. Invocation
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> |Column|n/a|n/a|
> |Cell|ExpressionLanguage|URI|
> h2. Manual Acceptance Test
> - Switching between DRG and Grid editor, check proper fields shown
> - Switching between rows, columns, cells in Grid editor, check proper fields
> -- In same expression kind
> -- Across different expression kinds
> - Clear expression kind
> - Read only mode - older asset version
> - All Grid specific properties saved
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3109) [DMN Designer] Add additional Properties to drill-down
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3109?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3109:
-----------------------------------
Description:
The Properties Panel currently shows properties for Stunner-level "graph" components.
*Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Literal expression
||Selected item||Properties panel items||type|| ||
|Cell|ExpressionLanguage|URI|(/)|
h3. Context
||Selected item||Properties panel items||type||
|Row|type Ref|ItemDefinition ref (same which applies to Key Cell|
|Column|n/a|n/a|
|Key Cell|type Ref|ItemDefinition ref|
|Value Cell|ExpressionLanguage|URI|
h3. Decision Table
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
| Input Column|Constraints|Text field|
|Output Column|Output values|Unary tests|
|Output Column|Default Output|expression|
|Cell|ExpressionLanguage|URI|
h3. Relation
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|type Ref|ItemDefinition ref|
|Cell|ExpressionLanguage|URI|
h3. Function
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|n/a|n/a|
|Cell|ExpressionLanguage|URI|
h3. Invocation
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|n/a|n/a|
|Cell|ExpressionLanguage|URI|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
was:
The Properties Panel currently shows properties for Stunner-level "graph" components.
*Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Literal expression
||Selected item||Properties panel items||type||
|Cell|ExpressionLanguage|URI|
h3. Context
||Selected item||Properties panel items||type||
|Row|type Ref|ItemDefinition ref (same which applies to Key Cell|
|Column|n/a|n/a|
|Key Cell|type Ref|ItemDefinition ref|
|Value Cell|ExpressionLanguage|URI|
h3. Decision Table
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
| Input Column|Constraints|Text field|
|Output Column|Output values|Unary tests|
|Output Column|Default Output|expression|
|Cell|ExpressionLanguage|URI|
h3. Relation
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|type Ref|ItemDefinition ref|
|Cell|ExpressionLanguage|URI|
h3. Function
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|n/a|n/a|
|Cell|ExpressionLanguage|URI|
h3. Invocation
||Selected item||Properties panel items||type||
|Row|n/a|n/a|
|Column|n/a|n/a|
|Cell|ExpressionLanguage|URI|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
> [DMN Designer] Add additional Properties to drill-down
> ------------------------------------------------------
>
> Key: DROOLS-3109
> URL: https://issues.jboss.org/browse/DROOLS-3109
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The Properties Panel currently shows properties for Stunner-level "graph" components.
> *Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
> h2. Properties on the Grid Level
> The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
> (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
> h3. Literal expression
> ||Selected item||Properties panel items||type|| ||
> |Cell|ExpressionLanguage|URI|(/)|
> h3. Context
> ||Selected item||Properties panel items||type||
> |Row|type Ref|ItemDefinition ref (same which applies to Key Cell|
> |Column|n/a|n/a|
> |Key Cell|type Ref|ItemDefinition ref|
> |Value Cell|ExpressionLanguage|URI|
> h3. Decision Table
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> | Input Column|Constraints|Text field|
> |Output Column|Output values|Unary tests|
> |Output Column|Default Output|expression|
> |Cell|ExpressionLanguage|URI|
> h3. Relation
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> |Column|type Ref|ItemDefinition ref|
> |Cell|ExpressionLanguage|URI|
> h3. Function
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> |Column|n/a|n/a|
> |Cell|ExpressionLanguage|URI|
> h3. Invocation
> ||Selected item||Properties panel items||type||
> |Row|n/a|n/a|
> |Column|n/a|n/a|
> |Cell|ExpressionLanguage|URI|
> h2. Manual Acceptance Test
> - Switching between DRG and Grid editor, check proper fields shown
> - Switching between rows, columns, cells in Grid editor, check proper fields
> -- In same expression kind
> -- Across different expression kinds
> - Clear expression kind
> - Read only mode - older asset version
> - All Grid specific properties saved
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM
by Jan Blizňák (Jira)
[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ]
Jan Blizňák edited comment on WFLY-11178 at 10/15/18 9:12 AM:
--------------------------------------------------------------
The result of this command (where you can find all whole stacktraces) was attached to the jira:
{noformat}
mvn -V verify -pl testsuite/integration/ws -Dts.basic -Dtest=WSTrustTestCase -DtestLogToFile=false | tee log.txt
{noformat}
was (Author: jbliznak):
The result of this command attached to the jira:
{noformat}
mvn -V verify -pl testsuite/integration/ws -Dts.basic -Dtest=WSTrustTestCase -DtestLogToFile=false | tee log.txt
{noformat}
> WSTrustTestCase failing on IBM
> ------------------------------
>
> Key: WFLY-11178
> URL: https://issues.jboss.org/browse/WFLY-11178
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 14.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
> Priority: Major
> Attachments: log.txt
>
>
> As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
> at javax.xml.validation.SchemaFactory.newInstance(Unknown Source)
> at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94)
> at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75)
> at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120)
> ... 102 more
> {code}
> It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM
by Jan Blizňák (Jira)
[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ]
Jan Blizňák commented on WFLY-11178:
------------------------------------
The result of this command attached to the jira:
{noformat}
mvn -V verify -pl testsuite/integration/ws -Dts.basic -Dtest=WSTrustTestCase -DtestLogToFile=false | tee log.txt
{noformat}
> WSTrustTestCase failing on IBM
> ------------------------------
>
> Key: WFLY-11178
> URL: https://issues.jboss.org/browse/WFLY-11178
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 14.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
> Priority: Major
> Attachments: log.txt
>
>
> As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
> at javax.xml.validation.SchemaFactory.newInstance(Unknown Source)
> at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94)
> at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75)
> at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120)
> ... 102 more
> {code}
> It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM
by Jan Blizňák (Jira)
[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ]
Jan Blizňák updated WFLY-11178:
-------------------------------
Attachment: log.txt
> WSTrustTestCase failing on IBM
> ------------------------------
>
> Key: WFLY-11178
> URL: https://issues.jboss.org/browse/WFLY-11178
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 14.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
> Priority: Major
> Attachments: log.txt
>
>
> As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
> at javax.xml.validation.SchemaFactory.newInstance(Unknown Source)
> at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94)
> at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75)
> at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120)
> ... 102 more
> {code}
> It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3136) DMN Validation Decision Table Analysis
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-3136:
--------------------------------------
Summary: DMN Validation Decision Table Analysis
Key: DROOLS-3136
URL: https://issues.jboss.org/browse/DROOLS-3136
Project: Drools
Issue Type: Epic
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
· Table completeness (no gaps in the rules)
· Table consistency (overlaps properly handled by hit policy)
· Subsumption (rules that could be combined)
· Rule masking (in P tables where some rule is never the top priority)
· First normal form violation (no hit policy F or O; no duplicate rules)
· Second normal form violation (all inputs relevant to the rule)
· Third normal form violation (all inputs independent)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (ELY-1677) Elytron Bearer Token Authentication - Return a 401 on Invalid Token
by Tzahi Fadida (Jira)
[ https://issues.jboss.org/browse/ELY-1677?page=com.atlassian.jira.plugin.s... ]
Tzahi Fadida commented on ELY-1677:
-----------------------------------
Hi,
This is really problematic for us.
I currently have to logout from our SPA for 403 instead of just 401.
It would be great if it could return 401 for expired tokens.
Is there an expectation for a fix for the next wildfly version?
Thanks.
> Elytron Bearer Token Authentication - Return a 401 on Invalid Token
> -------------------------------------------------------------------
>
> Key: ELY-1677
> URL: https://issues.jboss.org/browse/ELY-1677
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Authentication Mechanisms
> Affects Versions: 1.7.0.CR1
> Reporter: Edward Stathopoulos
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 1.7.0.CR3
>
>
> *Issue*
> Currently, Elytron will send back a 403 Response when an invalid bearer token is sent. For the built-in JWT validator (the token validation we are using), this [includes a few checks like signature, expiration time, audience and issuer|https://github.com/wildfly-security/wildfly-elytron/blob/1.7.0.CR1...].
> It seems that the current [BearerTokenAuthenticationMechanism|https://github.com/wildfly-security/wi...] does not differentiate between failed authentication and failed authorization, returning a 403 in both cases. This produces conflicting and erroneous results. Did I fail to authenticate (say, expired JWT) or did I authenticate but do not have access to the resource in question?
> This would also be closer in line with [RFC 6750 (The OAuth 2.0 Authorization Framework: Bearer Token Usage)|https://tools.ietf.org/html/rfc6750#section-3] which includes an example of an expired (invalid) token.
> {quote}
> And in response to a protected resource request with an
> authentication attempt using an expired access token:
> HTTP/1.1 401 Unauthorized
> WWW-Authenticate: Bearer realm="example",
> error="invalid_token",
> error_description="The access token expired"
> {quote}
> *Potential Solution*
> Perhaps this could be ameliorated by something akin to the following change in BearerTokenAuthenticationMechanism::evaluateRequest by differentiating between failure to authorize and failure to authenticate the token. Merely a quick, unvetted example as I haven't had enough time to dig in to the source.
> {code}
> if (verifyCallback.isVerified()) {
> AuthorizeCallback authorizeCallback = new AuthorizeCallback(null, null);
> handleCallback(authorizeCallback);
> if (authorizeCallback.isAuthorized()) {
> httpBearer.debugf("Token authentication successful.");
> handleCallback(new IdentityCredentialCallback(new BearerTokenCredential(tokenEvidence.getToken()), true));
> handleCallback(AuthenticationCompleteCallback.SUCCEEDED);
> request.authenticationComplete();
> return;
> }
> else{
> httpBearer.debugf("Token authorization failed message.");
> request.authenticationFailed("Some token unauthorized message", response -> response.setStatusCode(FORBIDDEN));
> return;
> }
> }
> httpBearer.debugf("Token authentication failed.");
> request.authenticationFailed("Invalid bearer token", response -> response.setStatusCode(UNAUTHORIZED));
> return;
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months