Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of mgiammarco@gmail.com)
Date: Thu, 1 Mar 2012 08:13:33 -0800 (PST)
From: mgiammarco <mgiammarco@gmail.com>
To: users@camel.apache.org
Message-ID: <1330618413031-5528299.post@n5.nabble.com>
In-Reply-To: <1330560286376-5526421.post@n5.nabble.com>
References: <1330430597369-5521623.post@n5.nabble.com>
 <1330531577528-5525360.post@n5.nabble.com>
 <1330545757224-5525938.post@n5.nabble.com>
 <1330552825929-5526199.post@n5.nabble.com>
 <1330558042845-5526376.post@n5.nabble.com>
 <1330560286376-5526421.post@n5.nabble.com>
Subject: Re: How can Shiro be used with camel to limit access to a route?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,
I have already looked at shirosecurityinjector source code to find the name
of the header it adds to the message. Here it is:

public ByteSource encrypt() throws Exception {
        ByteArrayOutputStream stream = new  ByteArrayOutputStream();
        ObjectOutput serialStream = new ObjectOutputStream(stream);
        serialStream.writeObject(securityToken);
        ByteSource byteSource = cipherService.encrypt(stream.toByteArray(),
passPhrase);
        serialStream.close();
        stream.close();
        
        return byteSource;
    }

In effects it returns a "ByteSource" and not a String, but if I log the
message the token is clearly a String, probably because it is called
ByteSource toString().
Anyway I do some other tests and then I file a bug.

Thanks,
Mario

--
View this message in context: http://camel.465427.n5.nabble.com/How-can-Shiro-be-used-with-camel-to-limit-access-to-a-route-tp5521623p5528299.html
Sent from the Camel - Users mailing list archive at Nabble.com.