unable login via designer
Moderators: chulett, rschirm, roy
unable login via designer
Installed IIS 8.7 client on windows machine .
this machine has IIS v11.3 clients as well.
installation is successful
how ever when I try to login using dsadm from v8.7 to Linux server A
Failed to authenticate the current user against the select service tier .
peer not authentication; nested exception is javax.ssl.SSLunverified exception:peer not authenticated.
This is LDAP registers .
how ever using same dsadm I am able to connect from 8.7 client installed on another windows machine to linux server A.
any thoughts or suggestion please shed some light ...
Thanks in advance.
this machine has IIS v11.3 clients as well.
installation is successful
how ever when I try to login using dsadm from v8.7 to Linux server A
Failed to authenticate the current user against the select service tier .
peer not authentication; nested exception is javax.ssl.SSLunverified exception:peer not authenticated.
This is LDAP registers .
how ever using same dsadm I am able to connect from 8.7 client installed on another windows machine to linux server A.
any thoughts or suggestion please shed some light ...
Thanks in advance.
Last edited by peep on Wed Aug 19, 2015 1:49 pm, edited 1 time in total.
So... you are asking why you get an error attempting to use an 11.3 client to connect to an 8.7 server?
If that's not what you are asking, you'll need to be more precise regarding what "this machine" is and what "server A" is and where exactly the 8.7 client was installed and what that has to do with 11.3...
![Confused :?](./images/smilies/icon_confused.gif)
If that's not what you are asking, you'll need to be more precise regarding what "this machine" is and what "server A" is and where exactly the 8.7 client was installed and what that has to do with 11.3...
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
No ..
Installed client DS 8.7 on windows machine A and connected linux server successfully.
how ever did the same on windows machine B and while connecting to linux server I am encountered by below exceptions
Failed to authenticate the current user against the select service tier .
peer not authentication; nested exception is javax.ssl.SSLunverified exception:peer not authenticated.
To me this is more like Client issue ..
Installed client DS 8.7 on windows machine A and connected linux server successfully.
how ever did the same on windows machine B and while connecting to linux server I am encountered by below exceptions
Failed to authenticate the current user against the select service tier .
peer not authentication; nested exception is javax.ssl.SSLunverified exception:peer not authenticated.
To me this is more like Client issue ..
Re: unable login via designer
What did this mean? How does 11.3 come into the picture?peep wrote:this machine has 11.3 ..
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Re: unable login via designer
this windows machine has v11.3 DS client installed .
so basically both v11.3 and v8.7 clients are installed on our windows machines
so basically both v11.3 and v8.7 clients are installed on our windows machines
Re: unable login via designer
Code: Select all
peer not authenticated; nested exception is:
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
Exception type: java/rmi/RemoteException
Exception message: peer not authenticated; nested exception is:
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
Exception stack trace:
java.rmi.RemoteException: peer not authenticated; nested exception is:
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.ibm.iis.isf.security.auth.javahttp.JavaHttpAuthenticationService.login(JavaHttpAuthenticationService.java:72)
at com.ibm.iis.isf.security.auth.impl.HttpAuthenticationService.login(HttpAuthenticationService.java:117)
Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.ibm.jsse2.bc.getPeerCertificates(bc.java:133)
at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:572)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:640)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
at com.ibm.iis.isf.binding.javahttp.runtime.JavaHttpServiceCreator.callOperation(JavaHttpServiceCreator.java:436)
at com.ibm.iis.isf.security.auth.javahttp.JavaHttpAuthenticationService.login(JavaHttpAuthenticationService.java:59)
... 1 more
I asked because you've never been able to run two client versions at the same time, that's why in the past they gave you the MCM or Multi-Client Manager which allowed you to switch the active version.
HOWEVER, I'm not sure that's even possible any longer with the new topology. I'm going to need to rely on the kindness of (more informed) strangers here...
HOWEVER, I'm not sure that's even possible any longer with the new topology. I'm going to need to rely on the kindness of (more informed) strangers here...
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Hi Chulett I am sorry I know have confused you .
I am using MCM to connect to appropriate version.
It is possible to switch client versions to connect to appropriate server versions.
In this case is I am trying connect v8.7 server from v8.7 client .
In this v8.7 DS setup we are not using SSL or any https or any firewalls (fyi)
but the error message I see is SSL related .
Please scroll up to I have posted error message
I tried to put as much as info I can in the short message .
Thanks for taking your time out on this ...
I am using MCM to connect to appropriate version.
It is possible to switch client versions to connect to appropriate server versions.
In this case is I am trying connect v8.7 server from v8.7 client .
In this v8.7 DS setup we are not using SSL or any https or any firewalls (fyi)
but the error message I see is SSL related .
Please scroll up to I have posted error message
I tried to put as much as info I can in the short message .
Thanks for taking your time out on this ...
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
When you are logging in to DataStage using HTTP (port number 9080 by default), it temporarily switches to HTTPS (port number 9443 by default)while validating your password.
So it may be that your error is occurring during the password validation phase of your login.
Though why you are getting "peer not authenticated" messages is a bit of a mystery.
So it may be that your error is occurring during the password validation phase of your login.
Though why you are getting "peer not authenticated" messages is a bit of a mystery.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Re: unable login via designer
Root cause from my observation is I first installed v11.3 and then installed v8.7 .
So uninstalled and reinstalled v8.7 first then v11.3 .
Now both the versions are working perfectly .
sometimes I miss basic rules and start thinking for all other possible solutions .
Thanks for all your help...
So uninstalled and reinstalled v8.7 first then v11.3 .
Now both the versions are working perfectly .
sometimes I miss basic rules and start thinking for all other possible solutions .
Thanks for all your help...