I've looked through the other posts but keep getting the same error when trying to import swagger. I've also tried json and conversion to WADL but all lead to the same error (attached).screen-shot-2016-05-27-at-105737-am.png
Here is the yaml file:
# this is an example of example APIs swagger: "2.0" info: title: Sample description: Sample docs for API. version: "1.0" # the domain of the service host: api.sample.com # array of all schemes that your API supports schemes: - https # will be prefixed to all paths basePath: /v1 produces: - application/json paths: /users/profiles/creditCard: post: summary: Add Credit Card to Profile description: | Sample description parameters: - name: creditCard in: body description: Credit card details. schema: type: object properties: isMarkAsDefault: type: boolean description: Flag indicates whether the credit card should be set as the default credit card or not. creditCard: $ref: '#/definitions/CreditCard' tags: - User Profile - Credit Card responses: 200: description: Successful response schema: properties: profileStatus: type: integer description: | Indicates the profile status: - 4 = Signed-in - 2 = Recognized - 0 = Anonymous For recognized and anonymous profile status, all other outputs will be null default: description: Unexpected error schema: $ref: '#/definitions/Error' definitions: CreditCard: type: object properties: firstName: type: string lastName: type: string cardType: type: string cardNumber: type: string expirationMonth: type: integer expirationYear: type: integer Error: type: object properties: code: type: integer format: int32 message: type: string
Dear @Bobak Emamian ,
I have just tried above openApi Spec and it works perfectly fine. See rendered smartdocs here.
I also see it's not working in your developer portal. It's due to account which is communicating with Apigee Edge org. I see permissions issue related to provisioning of this account. That's the reason Management API calls are failing & resulting in above errors.
Unfortunately, I don't have access to fix same now, I need to work with Portal Provisioning Team to fix this issue. I can promise you to resolve this issue by Monday IST & I will make sure to get access to the system myself so that i can troubleshoot this kind of issues in future. Stay tuned @Bobak Emamian !
Update :
Issue has been fixed. Please verify & let us know if any. See comment below for more details.
Thanks so much!
@Bobak Emamian , We see that user account which is used to communicate with Edge is provisioned with incorrect role. We have fixed this issue & i have verified same in your developer portal. Keep us posted if any.
Some more updates @Bobak Emamian , When LDAP outage happened few days back , someone manually fixed affected accounts. When they are fixing they have added incorrect role. Thank you for highlighting same, We have fixed your developer portal issue & your query helped us to fix similar accounts. Thank you for asking & highlighting this issue.