|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
HTTP Basic Authentication |
« View previous topic :: View next topic » |
Author |
Message
|
alerajeshh |
Posted: Wed Sep 11, 2013 12:24 pm Post subject: HTTP Basic Authentication |
|
|
Acolyte
Joined: 19 Aug 2013 Posts: 55
|
Hi Iam a beginner for message broker...but still i managed to things by reading infocenter and other things.
The latest problem am facing is Basic Authentication...
My flow is like this MQinput ---> COmpute-->HTTP Req--->COmpute--->MQoutput
and other flow HTTP Input-->compute--->Http rep
the basic things for authentication is writing
SET OutputRoot.HTTPRequestHeader."Authorization" = 'Basic '||base64Encode(CAST('uname:pwd' as BLOB CCSID InputRoot.Properties.CodedCharSetId));
and selecting default propagation for Http input and http req nodes in Bar file
and i dnt knw hw it works..am trying to figure out ,
In mqinput security properties i have mentioned identity type tokens ,username ,password,issued by
in compute node i have even mentioned
SET OutputRoot.Properties.IdentityMappedType = 'usernameAndPassword';
SET OutputRoot.Properties.IdentityMappedToken = 'uname';
SET OutputRoot.Properties.IdentityMappedPassword = 'pwd';
SET OutputRoot.Properties.IdentityMappedIssuedBy = 'issuer';
now i really dontknow where does the basic authentication comes,,,,
its really hard to understand to learn from the topics,,,i have learned these from infocenter,,,how exactly the input should be and how exactly the output should be ? and how to validate the authentication ?am sending the httprequestheader.authorization where it is getting valid?
sorry but help me.... |
|
Back to top |
|
 |
Vitor |
Posted: Wed Sep 11, 2013 12:50 pm Post subject: Re: HTTP Basic Authentication |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
alerajeshh wrote: |
now i really dontknow where does the basic authentication comes,,,, |
It's performed by the flow being called. If that flow is coded to perform it.
alerajeshh wrote: |
how exactly the input should be and how exactly the output should be ? and how to validate the authentication ?am sending the httprequestheader.authorization where it is getting valid? |
HTTP is not a WMB concept but a web concept; there's any amount of stuff Mr Google can find for you which describes "how exactly the input should be and how exactly the output should be". The InfoCenter simply describes how WMB implements these concepts.
The web service call, whatever scheme you're using, is always authenticated at the receiving end; it's pointless for the sender to do it because that just means any hacker simply sends a token saying "it's ok, I'm not a hacker". The receiver (the http input node in your example) will verify the credentials supplied using whatever you have configured it to use. Again, WMB supports most of the common methods (like LDAP). _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|