Layer7 API Management

  • 1.  Issue Proxies Sync between Portal 4.2 & proxy

    Posted Nov 16, 2018 06:02 AM

    Hello,

     

    I'm installing   Portal 4.2 and Gateway in 9.3. We have have enroll initially the gateway cluster in the portal and we have reinstall the portal (intial reason was certificate problem) & Re enroll the Gateway.  regarding the proxy status  of the API & Plan are Sync Disruption. I have reinstall the otk on the gateways and the status in the proxies for the  apps are sync.

     

    Do you have an idea  why the API & Plan are in disrupt mode ?

     

    Thanks.

     

    Christophe 



  • 2.  Re: Issue Proxies Sync between Portal 4.2 & proxy

    Broadcom Employee
    Posted Nov 18, 2018 05:02 PM

    Dear Christophe KAUFFMANN,

    Re-enrollment is not officially supported yet.

    If you have a snapshot/backup before the last enrollment, it's the simplest way to go back to a clean proxy.

    If you cannot revert back for any reason, you may have to manually clean up the proxy before you can re-enroll.

     

    Try the following (but not 100% guarantee)

    - delete portal users in Internal Identity Provider
    - delete portal private keys
    - delete portal certificates
    - delete cluster wide properties for portal
    - delete schedule tasks of portal
    - delete Portal APIs (published from portal or from gateway)

    (if still fail to enroll, re-do the above, and uninstall the Oauth OTK for portal)

     

    Regards,

    Mark



  • 3.  Re: Issue Proxies Sync between Portal 4.2 & proxy

    Posted Nov 20, 2018 08:52 AM

    Hello

     

    I have clean the gateway & reinstall the otk addon. But the result is the same. The APP is sync but APIs and account plan  are in disruption.



  • 4.  Re: Issue Proxies Sync between Portal 4.2 & proxy

    Broadcom Employee
    Posted Nov 20, 2018 06:12 PM

    Hi, it's better to open a support ticket to check the logs to find the reason of sync failure



  • 5.  Re: Issue Proxies Sync between Portal 4.2 & proxy
    Best Answer

    Posted Nov 27, 2018 10:06 AM

    Hello

    Just to give a feedback. The portal was in 4.2.7.1. It seems to be a bug. The upgrade in 4.2.9.3 fix the issue.