Topic
  • 18 replies
  • Latest Post - ‏2016-04-06T19:09:05Z by vikkee
Gilles 39
Gilles 39
31 Posts

Pinned topic Process Designer 8.5.0.1... Process Center : peer not authenticated...

‏2013-12-10T19:32:08Z |

Hello all.

For the record. Could be of use.

After an upgrade from 8.5 to 8.5.0.1, I could not start any more the new Process Designer. I got a pop-up when trying to log in , displaying an error :

Erreur : Une erreur inattendue s'est produite lors de la tentative de connexion au composant Process Center : peer not authenticated

Edit2 : not a good idea : A hack in C:\IBM\ProcessDesigner\v8.5\eclipse.ini worked around the issue : removed the "s" from "https" :

BEFORE:   -Dcom.ibm.bpm.processcenter.url=https://my_process_center_host
AFTER:    -Dcom.ibm.bpm.processcenter.url=http://my_process_center_host

Edit1 : nope, it is not that : But the correct action to fix issue was to not forget after having applied fixpack 8.5.0.1 - to regenerate WAS http plugin in WAS admin console and propagate changes onto our offline frontal web server. Then no need any more to hack. It worked.

Bye.

Gilles

Updated on 2013-12-16T09:40:23Z at 2013-12-16T09:40:23Z by Gilles 39
  • Gilles 39
    Gilles 39
    31 Posts

    Re: Process Designer ... Process Center : peer not authenticated...

    ‏2013-12-11T11:03:23Z  

    Eventually, it was a false explanation I believed. "...peer not authenticated..." was not solved by plugin regeneration.

    Actually (Edit2) the switch in eclipse.ini from https to http, got IBM Process Designer (IPD) to ask me to trust a certificate "Invite d'échange de signature ssl". I said yes. It started fine. Then, having stopped IPD, (Edit2) switching back the eclipse.ini from http to https, got IPD to be able to start with no problem in proper https mode.

    Bye.

    Edit2 : https -> http : not a good idea.

    Updated on 2013-12-16T09:40:50Z at 2013-12-16T09:40:50Z by Gilles 39
  • Gilles 39
    Gilles 39
    31 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2013-12-16T10:01:16Z  

    Hello again.

    I turns out my little hack ( eclipse.ini : https - http -> https ) caused more troubles than solution. After having gone through the bad hack, all IBM Process Designer (IPD) tools could not connect at all to Process Center. Got a pop up :

    Error getting WsnNameService properties

    The IPD log C:\IBM\ProcessDesigner\orbtrc.11122013.1310.24.txt showed

    2013.12.11 09:43:56.418 com.ibm.ws.security.orbssl.WSSSLClientSocketFactoryImpl createSSLSocket IBM JDK ORB ORBRas ORBRas JSSL0130E:
                    java.io.IOException : Signale qu'une exception d'E-S s'est produite. Raison :  Read timed out Hôte distant : 10.xx.xx.xxx 
                    Port éloigné : 30308, p1=java.net.SocketTimeoutException: Read timed out

    We are running BPM PC on a WAS ND deployment with single node. The IP 10.xx.xx.xxx is the one of the the WAS node host. We first restarted the PC several times : it un-blocked the situation for already installed IPD. But after each new IPD installation ( and http hack ) the problem came back.

    Eventually, we fixed both peer not authenticated issue and WsnNamesService by providing a post IPD installation action based on Trust store problem when connecting from Process Designer to Process Center in IBM Business Process Manager (BPM) : We update IPD  trust.p12 with cert from WAS node. This way, we did not have the authentication problem with IPD. Thus we did not try anymore to hack i.e. to talk "http" to PC. It seams better because our PC is _not_ configured (in WAS admin console) to serve non secured connection, only "https". And the WsnNamesService issue does not happen anymore.

    Bye.

    Updated on 2013-12-19T13:48:16Z at 2013-12-19T13:48:16Z by Gilles 39
  • AndrewPaier
    AndrewPaier
    832 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2013-12-18T22:33:05Z  

    Hello again.

    I turns out my little hack ( eclipse.ini : https - http -> https ) caused more troubles than solution. After having gone through the bad hack, all IBM Process Designer (IPD) tools could not connect at all to Process Center. Got a pop up :

    Error getting WsnNameService properties

    The IPD log C:\IBM\ProcessDesigner\orbtrc.11122013.1310.24.txt showed

    2013.12.11 09:43:56.418 com.ibm.ws.security.orbssl.WSSSLClientSocketFactoryImpl createSSLSocket IBM JDK ORB ORBRas ORBRas JSSL0130E:
                    java.io.IOException : Signale qu'une exception d'E-S s'est produite. Raison :  Read timed out Hôte distant : 10.xx.xx.xxx 
                    Port éloigné : 30308, p1=java.net.SocketTimeoutException: Read timed out

    We are running BPM PC on a WAS ND deployment with single node. The IP 10.xx.xx.xxx is the one of the the WAS node host. We first restarted the PC several times : it un-blocked the situation for already installed IPD. But after each new IPD installation ( and http hack ) the problem came back.

    Eventually, we fixed both peer not authenticated issue and WsnNamesService by providing a post IPD installation action based on Trust store problem when connecting from Process Designer to Process Center in IBM Business Process Manager (BPM) : We update IPD  trust.p12 with cert from WAS node. This way, we did not have the authentication problem with IPD. Thus we did not try anymore to hack i.e. to talk "http" to PC. It seams better because our PC is _not_ configured (in WAS admin console) to serve non secured connection, only "https". And the WsnNamesService issue does not happen anymore.

    Bye.

    Thank you for the through explanation.  Sometimes posting these sort of problems can feel like shouting into the abyss.  Just wanted to say I saw the post and would be amazed if we don't see a customer with this problem in the next year.  Thank you for your writeup which will likely save us hours of diagnosis.

    ANDREW PAIER
    VICE PRESIDENT, LABS
    T: 512.600.3239 X 240 / apaier@bp-3.com / @apaier
    BP3 /// www.bp-3.com / Blogs / Twitter / LinkedIn / Google+

  • adabreu
    adabreu
    1 Post

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2013-12-19T21:08:53Z  

    Hi Gilles, I am going exactly through the same problem you faced but Im not clear of the steps you applied to solve it.

    In your text

    "Eventually, we fixed both peer not authenticated issue and WsnNamesService by providing a post IPD installation action based on Trust store problem when connecting from Process Designer to Process Center in IBM Business Process Manager (BPM) : We update IPD  trust.p12 with cert from WAS node. This way, we did not have the authentication problem with IPD. Thus we did not try anymore to hack i.e. to talk "http" to PC. It seams better because our PC is _not_ configured (in WAS admin console) to serve non secured connection, only "https". And the WsnNamesService issue does not happen anymore."

    the link applies to BPM 7.5.1, and more than one course of action.

    Would you tell me exactly the steps you took?

    Im also considering this technote: http://www-01.ibm.com/support/docview.wss?uid=swg21591625 regarding ports that must be enabled at the firewall

    Thanks a lot

  • Gilles 39
    Gilles 39
    31 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-01-09T10:59:47Z  
    • adabreu
    • ‏2013-12-19T21:08:53Z

    Hi Gilles, I am going exactly through the same problem you faced but Im not clear of the steps you applied to solve it.

    In your text

    "Eventually, we fixed both peer not authenticated issue and WsnNamesService by providing a post IPD installation action based on Trust store problem when connecting from Process Designer to Process Center in IBM Business Process Manager (BPM) : We update IPD  trust.p12 with cert from WAS node. This way, we did not have the authentication problem with IPD. Thus we did not try anymore to hack i.e. to talk "http" to PC. It seams better because our PC is _not_ configured (in WAS admin console) to serve non secured connection, only "https". And the WsnNamesService issue does not happen anymore."

    the link applies to BPM 7.5.1, and more than one course of action.

    Would you tell me exactly the steps you took?

    Im also considering this technote: http://www-01.ibm.com/support/docview.wss?uid=swg21591625 regarding ports that must be enabled at the firewall

    Thanks a lot

    Hi there.

    After my "failing" IPD installation, I collected the "working" trust.p12 file that I could find in the installation of IPD.

    Then I devised an installation procedure stating 1) install IPD as usual 2) run that litle script of mine that will "post install" i.e. repleace the out-of-the-box trust.p12 created by plain installation, with the the "working" one I collected before.

    The correct way to update this trust.p12 is explained in the doc Trust store problem when connecting from Process Designer to Process Center in IBM Business Process Manager (BPM).

    Yep : checking firewall with a plain telnet could help pin point your isuue.

    Regards.

  • MikeZilbergleyt
    MikeZilbergleyt
    15 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-01-15T17:47:45Z  

    Hi,

    I found that if you install PD using command line, these problem do not apply!

    <PD_UNZIPPED>\installProcessDesigner_admin.bat C:\IBM\ProcessDesigner\v8501

    Thanks,

    Mike Z

  • Gilles 39
    Gilles 39
    31 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-01-15T17:58:36Z  

    Hi,

    I found that if you install PD using command line, these problem do not apply!

    <PD_UNZIPPED>\installProcessDesigner_admin.bat C:\IBM\ProcessDesigner\v8501

    Thanks,

    Mike Z

    Hi.

    FI: I used the script on the command line. And had the problem.

    Bye.

  • David Bailie
    David Bailie
    47 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-01-16T00:56:09Z  

    I have a new 8.5.0.1 environment, and when I installed the Process Designer (using install manager directly so I could install it on a vm with other PDs) I got a SSL Signer exchange prompt about the SSL signer from target not not found in trust store etc/trust.p12.  When I accepted the prompt to add the signer to the trust store the login to the server failed with "Error getting WsnNameService properties". I then tried copying the trust.p12 that was included with the PD zip file from the server and still got the same error.  Others were getting the same error from previously working PDs, so we restarted the server and then everyone could log in.  

     
    I thought this was odd, so I tested again.  I replaced the PD's etc/trust.p12 with the original and got the same SSL prompt and WsnNameService error.  I switched to the etc/trust.p12 that came from the server and still got the WsnNameService error.  I restarted the server again and could log in.  I wanted to see what was going on, so I tailed the logs and tried again and everything worked fine the third time - I accepted the SSL prompt and was logged in - couldn't reproduce the WsnNameService error.
     
    I looked at the old logs and I think this is the related exception on the server:
    [1/15/14 17:25:18:216 EST] 00000034 SystemErr     R Exception in thread "LT=1:P=186297:O=0:port=9405" java.lang.NoSuchMethodError: com/ibm/CORBA/iiop/OrbTrcLogger.exception(JLjava/lang/Object;Ljava/lang/String;Ljava/lang/Throwable;)V
    [1/15/14 17:25:18:216 EST] 00000034 SystemErr     R  at com.ibm.ws.security.orbssl.WSSSLServerSocketFactoryImpl.getPeerCertificateChain(WSSSLServerSocketFactoryImpl.java:580)
    [1/15/14 17:25:18:216 EST] 00000034 SystemErr     R  at com.ibm.ws.orbimpl.transport.WSSSLTransportConnection$1.run(WSSSLTransportConnection.java:142)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.ws.orbimpl.transport.WSSSLTransportConnection.<init>(WSSSLTransportConnection.java:139)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.ws.orbimpl.transport.WSTransport.createTransportConnection(WSTransport.java:1029)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.rmi.transport.ListenerThread.run(ListenerThread.java:201)
     
    Some searching turned up:


    Which all look like issues on older version of WAS - except maybe that last one - or I guess it could also be a regression.

  • sergmmm
    sergmmm
    5 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-03-20T09:35:16Z  

    I have a new 8.5.0.1 environment, and when I installed the Process Designer (using install manager directly so I could install it on a vm with other PDs) I got a SSL Signer exchange prompt about the SSL signer from target not not found in trust store etc/trust.p12.  When I accepted the prompt to add the signer to the trust store the login to the server failed with "Error getting WsnNameService properties". I then tried copying the trust.p12 that was included with the PD zip file from the server and still got the same error.  Others were getting the same error from previously working PDs, so we restarted the server and then everyone could log in.  

     
    I thought this was odd, so I tested again.  I replaced the PD's etc/trust.p12 with the original and got the same SSL prompt and WsnNameService error.  I switched to the etc/trust.p12 that came from the server and still got the WsnNameService error.  I restarted the server again and could log in.  I wanted to see what was going on, so I tailed the logs and tried again and everything worked fine the third time - I accepted the SSL prompt and was logged in - couldn't reproduce the WsnNameService error.
     
    I looked at the old logs and I think this is the related exception on the server:
    [1/15/14 17:25:18:216 EST] 00000034 SystemErr     R Exception in thread "LT=1:P=186297:O=0:port=9405" java.lang.NoSuchMethodError: com/ibm/CORBA/iiop/OrbTrcLogger.exception(JLjava/lang/Object;Ljava/lang/String;Ljava/lang/Throwable;)V
    [1/15/14 17:25:18:216 EST] 00000034 SystemErr     R  at com.ibm.ws.security.orbssl.WSSSLServerSocketFactoryImpl.getPeerCertificateChain(WSSSLServerSocketFactoryImpl.java:580)
    [1/15/14 17:25:18:216 EST] 00000034 SystemErr     R  at com.ibm.ws.orbimpl.transport.WSSSLTransportConnection$1.run(WSSSLTransportConnection.java:142)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.ws.orbimpl.transport.WSSSLTransportConnection.<init>(WSSSLTransportConnection.java:139)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.ws.orbimpl.transport.WSTransport.createTransportConnection(WSTransport.java:1029)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.rmi.transport.ListenerThread.run(ListenerThread.java:201)
     
    Some searching turned up:


    Which all look like issues on older version of WAS - except maybe that last one - or I guess it could also be a regression.

    Here is my experience - 

    I have this exact same problem and it's in PD 8.5.0.1

    Restart helps but what is more interesting is that if I go to WAS admin console -> cell trust store, remove one of the certificates (it does not matter which one) and then re-added it back, so, the trust store was modified.

    I can now login to PD again without restart!!..............
    This is some kind of weird WAS bug I think...
     
    I also tried to just touch the trust.p12 file on the filesystem using the touch Linux command but this didn't make a difference. I still could NOT login but once modified through WAS admin console - it again works...

    PD works for me for a few hours and then once more developers start login in and using PD at some point it stops working again. I "touch" (remove and add any certificate) the trust store in WAS again and it starts working again. (no restart is required)

  • sergmmm
    sergmmm
    5 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-03-20T09:36:36Z  

    I have a new 8.5.0.1 environment, and when I installed the Process Designer (using install manager directly so I could install it on a vm with other PDs) I got a SSL Signer exchange prompt about the SSL signer from target not not found in trust store etc/trust.p12.  When I accepted the prompt to add the signer to the trust store the login to the server failed with "Error getting WsnNameService properties". I then tried copying the trust.p12 that was included with the PD zip file from the server and still got the same error.  Others were getting the same error from previously working PDs, so we restarted the server and then everyone could log in.  

     
    I thought this was odd, so I tested again.  I replaced the PD's etc/trust.p12 with the original and got the same SSL prompt and WsnNameService error.  I switched to the etc/trust.p12 that came from the server and still got the WsnNameService error.  I restarted the server again and could log in.  I wanted to see what was going on, so I tailed the logs and tried again and everything worked fine the third time - I accepted the SSL prompt and was logged in - couldn't reproduce the WsnNameService error.
     
    I looked at the old logs and I think this is the related exception on the server:
    [1/15/14 17:25:18:216 EST] 00000034 SystemErr     R Exception in thread "LT=1:P=186297:O=0:port=9405" java.lang.NoSuchMethodError: com/ibm/CORBA/iiop/OrbTrcLogger.exception(JLjava/lang/Object;Ljava/lang/String;Ljava/lang/Throwable;)V
    [1/15/14 17:25:18:216 EST] 00000034 SystemErr     R  at com.ibm.ws.security.orbssl.WSSSLServerSocketFactoryImpl.getPeerCertificateChain(WSSSLServerSocketFactoryImpl.java:580)
    [1/15/14 17:25:18:216 EST] 00000034 SystemErr     R  at com.ibm.ws.orbimpl.transport.WSSSLTransportConnection$1.run(WSSSLTransportConnection.java:142)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.ws.orbimpl.transport.WSSSLTransportConnection.<init>(WSSSLTransportConnection.java:139)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.ws.orbimpl.transport.WSTransport.createTransportConnection(WSTransport.java:1029)
    [1/15/14 17:25:18:219 EST] 00000034 SystemErr     R  at com.ibm.rmi.transport.ListenerThread.run(ListenerThread.java:201)
     
    Some searching turned up:


    Which all look like issues on older version of WAS - except maybe that last one - or I guess it could also be a regression.

    Here is my experience - 

    I have this exact same problem and it's in PD 8.5.0.1

    Restart helps but what is more interesting is that if I go to WAS admin console -> cell trust store, remove one of the certificates (it does not matter which one) and then re-added it back, so, the trust store was modified.

    I can now login to PD again without restart!!..............
    This is some kind of weird WAS bug I think...
     
    I also tried to just touch the trust.p12 file on the filesystem using the touch Linux command but this didn't make a difference. I still could NOT login but once modified through WAS admin console - it again works...

    PD works for me for a few hours and then once more developers start login in and using PD at some point it stops working again. I "touch" (remove and add any certificate) the trust store in WAS again and it starts working again. (no restart is required)

  • RyanCox
    RyanCox
    15 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-03-24T19:15:29Z  

    I've had this same problem on two different BPM 8.5.0.1 environments now.

    I've tried the two solutions that have worked for others in this thread and neither of these resolved the problem:

    I've seen this "Error getting WsnNameService properties" problem occur in two different situations:

    1. After a fresh configuration of a BPM 8.5.0.1 Process Center deployment environment.

      In this scenario, users were able to connect from Process Designer initially, and then without any changes to the SSL config on the server, *something* started causing the "Error getting WsnNameService properties" error from all Process Designer installations that were previously working.

      For this scenario, a restart of the BPM Process Center deployment environment fixes this problem, and all Process Designer installations are now able to connect again...for some period of time. I haven't found a pattern yet to what triggers the problem again, but at some point (around two-three days usually), the problem crops up again, and I simply restart the deployment environment and all is good. This is a terrible solution though for maintaining a shared development environment.
       
    2. After configuring single sign-on between the BPM Process Center cell and another WAS cell. (For example, this is required if exposing human services as JSR286 portlets in WebSphere Portal).

      In this scenario, I haven't found a solution to this problem yet that allows Process Designer to connect to the Process Center. A restart of the cell doesn't solve anything. The only way I've recovered from this scenario is by configuring a new Process Center deployment environment. (which sucks).

    Any suggestions are very welcome. I will be submitting a PMR on this and will update this thread if something useful comes of it.

  • sergmmm
    sergmmm
    5 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-03-25T17:15:19Z  
    • RyanCox
    • ‏2014-03-24T19:15:29Z

    I've had this same problem on two different BPM 8.5.0.1 environments now.

    I've tried the two solutions that have worked for others in this thread and neither of these resolved the problem:

    I've seen this "Error getting WsnNameService properties" problem occur in two different situations:

    1. After a fresh configuration of a BPM 8.5.0.1 Process Center deployment environment.

      In this scenario, users were able to connect from Process Designer initially, and then without any changes to the SSL config on the server, *something* started causing the "Error getting WsnNameService properties" error from all Process Designer installations that were previously working.

      For this scenario, a restart of the BPM Process Center deployment environment fixes this problem, and all Process Designer installations are now able to connect again...for some period of time. I haven't found a pattern yet to what triggers the problem again, but at some point (around two-three days usually), the problem crops up again, and I simply restart the deployment environment and all is good. This is a terrible solution though for maintaining a shared development environment.
       
    2. After configuring single sign-on between the BPM Process Center cell and another WAS cell. (For example, this is required if exposing human services as JSR286 portlets in WebSphere Portal).

      In this scenario, I haven't found a solution to this problem yet that allows Process Designer to connect to the Process Center. A restart of the cell doesn't solve anything. The only way I've recovered from this scenario is by configuring a new Process Center deployment environment. (which sucks).

    Any suggestions are very welcome. I will be submitting a PMR on this and will update this thread if something useful comes of it.

    Ryan and for those who concerned - I still believe there is a regression in WAS/BPM hidden here BUT we resolved it by using the "httpProtocolOnly" switch, setting it to true. This basically makes PD -> PC communication to be through HTTP/HTTPS calls only and eliminates the requirement for ORB/RMI. Since then we have not seen wsname service error anymore because this error is ORB specific (it even generates orb trace). hope this helps.

    http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r5m0/index.jsp?topic=%2Fcom.ibm.wbpm.admin.doc%2Ftopics%2Ftcfg_httpprotocol_config.html

  • RyanCox
    RyanCox
    15 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-03-25T22:35:17Z  
    • sergmmm
    • ‏2014-03-25T17:15:19Z

    Ryan and for those who concerned - I still believe there is a regression in WAS/BPM hidden here BUT we resolved it by using the "httpProtocolOnly" switch, setting it to true. This basically makes PD -> PC communication to be through HTTP/HTTPS calls only and eliminates the requirement for ORB/RMI. Since then we have not seen wsname service error anymore because this error is ORB specific (it even generates orb trace). hope this helps.

    http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r5m0/index.jsp?topic=%2Fcom.ibm.wbpm.admin.doc%2Ftopics%2Ftcfg_httpprotocol_config.html

    Thanks Sergii!

    Setting the Process Center httpProtocolOnly=true fixed this problem on both of my environments.

    I submitted a support request (00874,004,000) on this issue and they pointed back to this forum thread with your latest comment :-)

  • AleToledo
    AleToledo
    5 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-04-08T22:29:55Z  
    • sergmmm
    • ‏2014-03-25T17:15:19Z

    Ryan and for those who concerned - I still believe there is a regression in WAS/BPM hidden here BUT we resolved it by using the "httpProtocolOnly" switch, setting it to true. This basically makes PD -> PC communication to be through HTTP/HTTPS calls only and eliminates the requirement for ORB/RMI. Since then we have not seen wsname service error anymore because this error is ORB specific (it even generates orb trace). hope this helps.

    http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r5m0/index.jsp?topic=%2Fcom.ibm.wbpm.admin.doc%2Ftopics%2Ftcfg_httpprotocol_config.html

    Hello,

    Our testing environment has presented the same issue for the last couple of days.

    First, we started seeing the WSNameService error that was mentioned earlier in the thread. After I applied the httpProtocolOnly solution that sergmmm wrote, we solved the WSNameService error and the developers can use the Process Designer again. (Thank You!!!)

    But there is a "peer not authenticated" message appearing each time someone tries to open any kind of service in the Process Designer. Oddly enough they just click on the OK button of the message, it disappears and it doesn't do anything else.

    The developers can work for now with the issue, but it's kind of annoying. Is anyone having the same behavior on your PD?

  • sergmmm
    sergmmm
    5 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-04-17T12:32:29Z  
    • AleToledo
    • ‏2014-04-08T22:29:55Z

    Hello,

    Our testing environment has presented the same issue for the last couple of days.

    First, we started seeing the WSNameService error that was mentioned earlier in the thread. After I applied the httpProtocolOnly solution that sergmmm wrote, we solved the WSNameService error and the developers can use the Process Designer again. (Thank You!!!)

    But there is a "peer not authenticated" message appearing each time someone tries to open any kind of service in the Process Designer. Oddly enough they just click on the OK button of the message, it disappears and it doesn't do anything else.

    The developers can work for now with the issue, but it's kind of annoying. Is anyone having the same behavior on your PD?

    AleToledo - 

    peer not authenticated typically means that there is something wrong with your certificates configuration

    if you are using self-signed certificates you may want to install root self-signed certificate into your trust.p12 file that is located in PD_DIR\etc

    let me know if this helps.

    --Sergei

  • sergmmm
    sergmmm
    5 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-04-22T14:43:32Z  

    See also article I published here:

    https://bp3.zendesk.com/hc/en-us/articles/202010816-IBM-BPM-8-5-0-1-Process-Designer-Error-getting-WsnNameService-properties

  • AleToledo
    AleToledo
    5 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2014-04-30T16:19:02Z  
    • sergmmm
    • ‏2014-04-17T12:32:29Z

    AleToledo - 

    peer not authenticated typically means that there is something wrong with your certificates configuration

    if you are using self-signed certificates you may want to install root self-signed certificate into your trust.p12 file that is located in PD_DIR\etc

    let me know if this helps.

    --Sergei

    Thx for the response Sergei.

    We tried that approach, when you change the certificate inside the PD it asks you to accept the new certificate the first time you use the PD.

    What we discovered is that it is not enough to say "yes" to everything. In our case we had to install the certificate manually (using view certificate>install certificate option). When we did that the problem was gone.

  • vikkee
    vikkee
    51 Posts

    Re: Process Designer 8.5.0.1... Process Center : peer not authenticated...

    ‏2016-04-06T19:09:05Z  

    Came to this post after I got a peer autentication error on a 8501 process designer. While I was reading all the answers here, I asked my colleague to "Re-install" it to a different folder once again, and it just worked fine. It was the same installable zip file, and it logged in just fine. So try re-installing once before you try anything extraordinary and it may work well.