We have created a service and added 'Set Portal Managed Service' assertion at the top of the policy.
We moved the policy from Dev to QA but the API is not available in Portal to enable it.
Along with this there was another api with same configurations which is available to enable and publish.
What could be the reason for not published on Portal?
Is there any limit on Service name length? Our service name is something similar to below:
This issue is resolved but forget to update the resolution.
One of our developer copied the 'set as portal Managed service' assertion from different policy which is already published.
'set as portal Managed service' assertion generates unique GUID which should be unique across a Developer portal. As this value is conflicting with another service our policy was not published on portal. Replacing this assertion with new one resolves the issue.
Lesson: Never copy 'Set As portal Managed Service' assertion from different policies.
Hi Kareem.shaik7 ,
Thank you for sharing the solution. This would have been a very common error that anyone could have done. Glad you were able to get to the bottom of this one.
Lesson: Never copy 'Set As portal Managed Service' assertion from different policies