[JBoss JIRA] (ELY-382) Add SASL server factory which has the ability to set a SecurityIdentity during authentication tasks
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-382?page=com.atlassian.jira.plugin.sy... ]
David Lloyd resolved ELY-382.
-----------------------------
Resolution: Rejected
On second thought, I'm rejecting this and throwing away the implementation.
The reason is that the callback handler is the thing which needs to track identity. The {{ServerAuthenticationContext}} should be capturing the active {{SecurityIdentity}} on instantiation, and maintaining an identity throughout the authentication process.
I will create a new JIRA, and a state machine diagram to illustrate the expected behavior of the authentication context.
> Add SASL server factory which has the ability to set a SecurityIdentity during authentication tasks
> ---------------------------------------------------------------------------------------------------
>
> Key: ELY-382
> URL: https://issues.jboss.org/browse/ELY-382
> Project: WildFly Elytron
> Issue Type: Task
> Components: SASL
> Reporter: David Lloyd
> Assignee: David Lloyd
>
> Add SASL server factory which has the ability to set a SecurityIdentity during authentication tasks. This is necessary so that (for example) EXTERNAL can perform authorization checks.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
- 1
- 0
[JBoss JIRA] (ELY-382) Add SASL server factory which has the ability to set a SecurityIdentity during authentication tasks
by David Lloyd (JIRA)
David Lloyd created ELY-382:
-------------------------------
Summary: Add SASL server factory which has the ability to set a SecurityIdentity during authentication tasks
Key: ELY-382
URL: https://issues.jboss.org/browse/ELY-382
Project: WildFly Elytron
Issue Type: Task
Components: SASL
Reporter: David Lloyd
Assignee: David Lloyd
Add SASL server factory which has the ability to set a SecurityIdentity during authentication tasks. This is necessary so that (for example) EXTERNAL can perform authorization checks.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
- 1
- 0
[JBoss JIRA] (WFLY-5479) rest api mashall object to json default not ignore null fileds
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5479?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-5479.
----------------------------------
Fix Version/s: (was: 10.0.0.CR5)
Resolution: Rejected
Current behavior is expected. RESTeasy uses Jackson 2 for serialization, please refer to the Jackson docs for how to change this behavior.
> rest api mashall object to json default not ignore null fileds
> --------------------------------------------------------------
>
> Key: WFLY-5479
> URL: https://issues.jboss.org/browse/WFLY-5479
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 10.0.0.Beta1, 10.0.0.Beta2, 10.0.0.CR1, 10.0.0.CR2
> Reporter: henry hu
> Labels: jboss
>
> mashall object to Json default not ignore null fileds,but mashall to xml is ok .
> "user": {
> "id": 26357,
> "gameId": null,
> "userIds": null,
> "userName": "testn008",
> "status": 1,
> "password": null,
> "payPassword": null,
> "qq": null,
> "email": null,
> "userType": 16,
> "level": 0,
> "subCompany": null,
> "majorShareholder": null,
> "sharehoder": null,
> "majorAgent": null,
> "agent": null,
> "nickName": "sdfs",
> "cellPhoneNumber": null,
> "createTime": "2015-05-08 20:32:37",
> "currency": "CNY",
> "registerIp": "127.0.0.1",
> "lastLoginIP": "127.0.0.1",
> "lastLoginTime": 1444146936000,
> "roles": [],
> "roleIds": [],
> "userCount": 0,
> "fromId": null,
> "fromUrl": null,
> "hasUpdatePwd": 1,
> "isSpread": 0,
> "spreadType": null,
> "parentUserName": null,
> "memberCnt": null,
> "serverTime": "2015-10-06 23:58:40"
> },
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
- 1
- 0