API gateway Enrollment fails with UniqueKeyConflict error message

book

Article ID: 193510

calendar_today

Updated On:

Products

CA API Gateway API SECURITY CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7) CA API Gateway Enterprise Service Manager (Layer 7) STARTER PACK-7 CA Microgateway

Issue/Introduction

When enrolling API gateway   API Portal (4.5) to an API Gateway (10.0).

The enrollment fails with a UniqueKeyConflict .

targetUri="/1.0/policies/fa95364d3f5876ac66e53090b69a1498" type="POLICY"/>
            <l7:Mapping action="NewOrUpdate" errorType="UniqueKeyConflict" srcId="b4bff64ea3a845db60b78151a87dc1e2" type="POLICY">
                <l7:Properties>
                    <l7:Property key="ErrorMessage">
                        <l7:StringValue>(name) (internalTag, type)  must be unique</l7:StringValue>
                    </l7:Property>
                </l7:Properties>
            </l7:Mapping>
            <l7:Mapping action="NewOrExisting" actionTaken="CreatedNew" srcId="e1b68aeecf2e5c477d2fee2096af72cd"

OTK is installed and upgraded to latest version. 

Cause

There is nothing into the database related to the srcId="b4bff64ea3a845db60b78151a87dc1e2 .

Verify if you are using global policy especially message_recieved 

Environment

Release : 10.0

Component : API GATEWAY

Resolution

If there is already a global policy for "message_recieved" the gateway enrollment will fails as there can only be one global policy with this tag.

which relates to the error <l7:StringValue>(name) (internalTag, type)  must be unique</l7:StringValue>

You can only have one global policy for type message_recieved, and you have to delete it .