Re: [Dev] Management console login attempt fails for worker node, but backend log says successfully logged in

2014-08-05 Thread Nipuni Perera
Hi, I could get a not-null value for response above removing local transport in carbon.xml. Still it does not print the log.warn() message and it seems log level is set to ERROR in class AuthorizationHandler. If I change the log4j.properties file entry as follows; log4j.rootLogger=ERROR,

Re: [Dev] Management console login attempt fails for worker node, but backend log says successfully logged in

2014-08-04 Thread Nipuni Perera
Hi, Yes, AuthorizationHandler does isWorkerNode() check in invoke(MessageContext msgContext) method [1]. But this statement does not get hit when I debug. As per the below code, the second if statement does not execute as it returns from the first. As I debug from the worker node, the second if

Re: [Dev] Management console login attempt fails for worker node, but backend log says successfully logged in

2014-08-04 Thread Nipuni Perera
Isn't response object gets a null value a bug? On Mon, Aug 4, 2014 at 2:47 PM, Nipuni Perera nip...@wso2.com wrote: Hi, Yes, AuthorizationHandler does isWorkerNode() check in invoke(MessageContext msgContext) method [1]. But this statement does not get hit when I debug. As per the below

Re: [Dev] Management console login attempt fails for worker node, but backend log says successfully logged in

2014-08-03 Thread Johann Nallathamby
[Adding Sameera Azeez] On Fri, Aug 1, 2014 at 10:06 PM, Johann Nallathamby joh...@wso2.com wrote: On Fri, Aug 1, 2014 at 7:11 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi, It makes sense to block the management console access for worker nodes, so that the users get a clear idea that

Re: [Dev] Management console login attempt fails for worker node, but backend log says successfully logged in

2014-08-03 Thread Afkham Azeez
When admin services on worker nodes are tried to be called, we return a 403. On Sun, Aug 3, 2014 at 11:17 PM, Johann Nallathamby joh...@wso2.com wrote: [Adding Sameera Azeez] On Fri, Aug 1, 2014 at 10:06 PM, Johann Nallathamby joh...@wso2.com wrote: On Fri, Aug 1, 2014 at 7:11 PM,

[Dev] Management console login attempt fails for worker node, but backend log says successfully logged in

2014-08-01 Thread Nipuni Perera
Hi, I am working on jira issue[1]. I could reproduce the issue in a cluster with ELB, manager node and a worker node using ESB 4.8.0. When a login attempt is triggered, 1. login() method of AuthenticationAdmin.java (line 62 of [2]) set boolean values for isAuthenticated and isAuthorized.

Re: [Dev] Management console login attempt fails for worker node, but backend log says successfully logged in

2014-08-01 Thread Kasun Gajasinghe
Hi, It makes sense to block the management console access for worker nodes, so that the users get a clear idea that performing management operations in worker nodes is wrong. But do we really need to block access to back-end admin services? Is there a usecase where users might need to perform

Re: [Dev] Management console login attempt fails for worker node, but backend log says successfully logged in

2014-08-01 Thread Johann Nallathamby
On Fri, Aug 1, 2014 at 7:11 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi, It makes sense to block the management console access for worker nodes, so that the users get a clear idea that performing management operations in worker nodes is wrong. But do we really need to block access to