| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| problem configure mqsicreateconfigurableservice using LDAP |
« View previous topic :: View next topic » |
| Author |
Message
|
| gun41exe |
 Posted: Thu Jan 28, 2010 1:48 am Post subject: problem configure mqsicreateconfigurableservice using LDAP |
 |
|
Newbie
Joined: 26 Jan 2010
Posts: 4
|
Hi ...., I'm a newbe for message broker.
I'm trying to create webservice security in message broker authenticated using LDAP.
but the authentication is always fail in my SOAP message header I have specify the right user: wpsadmin and right password : 123
this is my ldap configuration:
| Quote: |
| mqsicreateconfigurableservice WBRK61_DEFAULT_BROKER -c SecurityProfiles -o LDAP -n authentication,authorization,propagation,authenticationConfig,authorizationConfig -v "LDAP,LDAP,TRUE,\"ldap://192.168.0.138:389/cn=users, dc=hanoman, dc=co, dc=id\"" |
I'm not sure that my configuration is true or false. but the configuration below used by us for our websphere process server, Secure administration, applications, and infrastructure > Standalone LDAP registry .
| Code: |
Host : 192.168.0.138
Port : 389
Base distinguished name (DN) : dc=hanoman, dc=co, dc=id
Bind distinguished name (DN) : cn=wpsadmin, cn=users, dc=hanoman, dc=co, dc=id
|
I need your help. Thanks |
|
| Back to top |
|
 |
| gun41exe |
| Posted: Thu Jan 28, 2010 10:03 pm Post subject: |
|
|
Newbie
Joined: 26 Jan 2010
Posts: 4
|
| Help me please .......... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 29, 2010 4:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
show the output of mqsireportproperties on the configurable service you created.
show the mqsisetdbparm command you ran to authorize broker to connect to the LDAP server.
Show the error log when the connection was attempted. |
|
| Back to top |
|
|
| skadaval |
| Posted: Fri Jan 29, 2010 11:02 pm Post subject: |
|
|
Novice
Joined: 26 Mar 2008
Posts: 15
|
| Even I face same problem with soap nodes.My issue resolved by adding 'security profile name', 'Provider Policy Bindings', 'Provider Policy set ' values to bar file properties and redeploy the updated Bar file. Now I am able to authenticate.what type of error you are getting... |
|
| 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
|
|
|
|
