akamai / akamai-apis Goto Github PK

Issue type

• Bug
• New feature request
• Improvement
• Documentation (description, summaries, general text field issues)

Which API?

/appsec/v1/configs/{configId}/versions/{versionNumber}/security-policies/{policyId}/rate-policies
a.k.a. get rate policy actions.

Issue

1. The response object is incorrectly named ratePolicies, but it should be ratePolicyActions.
2. The type for the id field is set to string, but it should be integer.

Context

We're building an application using client code generated from the API spec with openapi-generator. We're having to patch around errors in the Akamai API specs to get some of the API calls working.

Bugs: Steps to reproduce

https://github.com/akamai/akamai-apis/blob/main/apis/appsec/v1/schemas/rate-policy-actions.yaml#L11
https://github.com/akamai/akamai-apis/blob/main/apis/appsec/v1/schemas/rate-policy-actions.yaml#L24
https://github.com/akamai/akamai-apis/blob/main/apis/appsec/v1/examples/rate-policy-actions.json#L2

Possible solution

I'll raise a PR.

Additional information

Issue type

• Bug
• New feature request
• Improvement
• Documentation (description, summaries, general text field issues)

Which API?

CCUV3

Issue

The Python recipe for the Invalidate Content by URL or ARL references in the current API endpoint. It has tag when it should be URL.

Context

Incorrect sample was a little confusing, luckily I was able to catch it before doing testing.

Bugs: Steps to reproduce

Navigate to https://techdocs.akamai.com/purge-cache/recipes/invalidate-content-by-url-or-arl and click on the Python tab. Noticed that on line 13, that tag is reference not URL.

Possible solution

Update the documentation.

Additional information

The schema defines the allowed api accessLevels as a string

It should be an array of strings as described here https://techdocs.akamai.com/iam-api/reference/get-api-clients-users-allowed-apis

Issue type

• Bug
• New feature request
• Improvement
• Documentation (description, summaries, general text field issues)

Which API?

V3
List allowed apis for a user

Issue type

• Bug
• New feature request
• Improvement
• Documentation (description, summaries, general text field issues)

Issue

GTM states making a domain is the first step in the workflow.

1. To create a domain, you must pass a data center and a property.
2. To create a data center, you must pass a domain.
3. To create a property, you must pass a domain. This operation piggy-backs on a PUT.

Context

I'm a new user attempting to create my first domain. Can't. I am completely blocked.

Bugs: Steps to reproduce

• Domain create data center requirement of data center.
• Data center create requirement of domain - it's a path parameter.

Workflow states create a domain and then a data center.

1. Construct a POST domain call.
2. When you get to datacenters, I have no value to pass, passed it empty.
3. Failed with a 400.
4. Construct a POST data center call.
5. Can't. Path requirement is a domain.

Possible solution

Remove the requirement on create domain or from the path of data centers.

Additional information

This is nuts.

Issue type

• Bug
• New feature request
• Improvement
• Documentation (description, summaries, general text field issues)

Which API?

SiteShield API Get-SiteShieldByID

Issue

Based on the openapi schema, when i make a request, in case of 403 or 404 response status i can get status code inside response, but when i have response 200, i just have fetch info from API without status code inside response.

Context

I m trying to implement GitHub action to automatically update siteshield cidrs range for my project, but when there is no proposedCidrs it is failing, while i try to cover this edge case i want to check that when i make API call i got 200 status and empty proposedCidrs so i can be aware of that and my action will not fail. But i with Get-SiteShieldByID i cannot cover this 200 response status, as in response body no status field, as in 404 and 403

Bugs: Steps to reproduce

Possible solution

Update openapi schema, and Invoke-AkamaiRestMethod to get this info in 200 response.

Additional information

Issue type

• Bug
• New feature request
• Improvement
• Documentation (description, summaries, general text field issues)

Issue

I have to. make four calls to get all of the information I could toggle through in the GET resources set of calls. Each call gets a single type of information.

• Countries
• States
• Languages
• Time zones

Context

When setting up or managing users, I have to run anywhere from 2 to all of the GET calls, and I would like to send one call and get everything if I wanted or choose which came back. Would save time cycling through four calls.

Bugs: Steps to reproduce

N/A

Possible solution

Combine countries, states, languages, and time zones into one call and set them to a Boolean. True gives a user the info, false doesn't.

Additional information

This set of calls is a waste of time.

Issue type

• Bug
• New feature request
• Improvement
• Documentation (description, summaries, general text field issues)

Which API?

https://techdocs.akamai.com/iam-api/reference/post-api-clients

Issue

Missing clientSecret in credentials created by using che create api client api, by setting the createCredentials to true.
https://github.com/akamai/akamai-apis/blame/main/apis/identity-management/v3/openapi.json#L513

Context

Bugs: Steps to reproduce

Possible solution

Add clientSecret field to the credentials field inside the post api client response when createCredentials is set to true

Additional information

Issue type

• Bug
• New feature request
• Improvement
• Documentation (description, summaries, general text field issues)

Issue

Confused about what to pass in the ou field since it wasn't returned as part of my CSR info.

Description states, "Your organizational unit."

Context

Trying to create a new DV certificate.

Bugs: Steps to reproduce

N/A

Possible solution

Update description so I better understand what information to put in the value.

Additional information

I don't know how to use this based on the information provided.

Issue type

• Bug
• New feature request
• Improvement
• Documentation (description, summaries, general text field issues)

Issue

I am unable to manage PCI/SOC2 compliance as I'm a small business. As a customer of my business, I would like to store my payment method information for future purchases.

Context

Give customers a way to save their payment information. Feedback from our customers around this issue has been quite snarky, but we're too small to manage the issue ourselves.

Bugs: Steps to reproduce

N/A

Possible solution

As you're a big company with security services, create a secure vault to store information.

Additional information

Help the SMB, too. We are on the struggle bus.