On Oct 1, 2012, at 11:29 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
I noticed some interesting behavior with the 'isAuthenticated' function.
It returns TRUE even when the pipe is not authenticated, because a
wrong(or no) authenticator has been attached,
IMO it should return FALSE when no authenticator is attached. Even on
a 'pipe connection' where no auth is required, the
'isAuthenticated:false' would be still wrong, as the connection is not
authenticated - since not required...
Any thoughts ?
Yes, this is a good point. I think in the rush to get something working, i have combined
isAuthenticated with something like hasAuthenticator which is wrong. This is still being
worked out, along with "privatizing" methods and none of the docs have been
written yet so give me a little more time and this will be straightened out.
Of course, this brings up the question if there should be some
'callback' that is invoke when the 'pipe' receives a 401. To indicate
'wrong' (or no) auth provided.. ?!
That is what the statusCode options is for so that not only 401 but any specific status
code can be handled appropriately. Again, once the docs are done this should be clearer.
aerogear-dev mailing list