Layer7 API Management

  • Private Community

  • 1.  GMU migratein Bad Request HTTP 400 Bad Request

    Posted Oct 29, 2018 10:53 AM

    Hi Team,

    we are getting bad request error while doing migratein, can you please help me to fix this issue.

     

    error logs

    Execution failed. Reason: Test migrate in failed: Bad Request HTTP 400 Bad Request. Caused by: cvc-complex-type.2.4.a: Invalid content was found starting with element 'l7:Writable'. One of '{"http://ns.l7tech.com/2010/04/gateway-management":Extension, WC[##other:"http://ns.l7tech.com/2010/04/gateway-management"], "http://ns.l7tech.com/2010/04/gateway-management":SourceType, "http://ns.l7tech.com/2010/04/gateway-management":ServerUrls}' is expected.

     

    --Thank you.



  • 2.  Re: GMU migratein Bad Request HTTP 400 Bad Request

    Broadcom Employee
    Posted Oct 29, 2018 11:04 AM

    Hi Uday 

     

    I would advice to raise a support case for this , so you can share in detail what you are migration and how.

    The message says the content is invalid but without having all the details it is impossible to tell what is wrong .

     

    Regards

    Dirk



  • 3.  Re: GMU migratein Bad Request HTTP 400 Bad Request

    Posted Oct 29, 2018 11:42 AM

    we are trying to migrate folder ( in folder we have lot of services ) while running migratein command ..its displaying on the screen.

    sample command :

     

    ./GatewayMigrationUtility.sh migrateIn -h <hostname> -u <username> --plaintextPassword <password> --bundle /tmp/test.xml --plaintextEncryptionPassphrase <password> --trustCertificate --trustHostname -results /tmp/test_results.xml --destFolder '<folderpath>'



  • 4.  Re: GMU migratein Bad Request HTTP 400 Bad Request

    Posted Oct 29, 2018 11:54 AM

    we can able to find below xml tag(l7:Writable) in migrateout bundle but unfortunately my policy is not using any identity provider, why its exporting ldap configurations ? and if export also, why its failing ? please help me to understand the issue where it is.

     

    <l7:LdapIdentityProviderDetail>
    <l7:Writable>false</l7:Writable>
    <l7:SourceType>GenericLDAP</l7:SourceType>
    <l7:ServerUrls>
    <l7:StringValue>ldaps://localhost:636</l7:StringValue>
    </l7:ServerUrls>
    <l7:UseSslClientAuthentication>false</l7:UseSslClientAuthentication>
    <l7:SearchBase>dc=sc,dc=enterprise</l7:SearchBase>
    <l7:BindDn>test</l7:BindDn>



  • 5.  Re: GMU migratein Bad Request HTTP 400 Bad Request

    Broadcom Employee
    Posted Oct 30, 2018 05:23 AM

    Hi Uday,

     

    I'm working with you on this issue in a support case. I will update this thread with our findings afterwards.



  • 6.  Re: GMU migratein Bad Request HTTP 400 Bad Request
    Best Answer

    Posted Nov 01, 2018 11:05 AM

    Hi All,

    This issue has been resolved with GMU1.5 version, the issue was occurred due to GUM version.