Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EW CLI auth does not support wildcard domains nor propertyId #71

Open
guillaume-fr opened this issue Mar 14, 2022 · 1 comment · May be fixed by #72
Open

EW CLI auth does not support wildcard domains nor propertyId #71

guillaume-fr opened this issue Mar 14, 2022 · 1 comment · May be fixed by #72

Comments

@guillaume-fr
Copy link

Edgeworkers CLI does not allow generating a token for a wildcard domain.

akamai ew auth '*.example.com'
We get the following error
ERROR: Creating auth token with secret is deprecated with version CLI 1.1.0. Please use your host name to create an authentication token.

We should update or remove isValidDomain(hostName) check
https://github.com/akamai/cli-edgeworkers/blob/master/src/edgeworkers/ew-cli-main.ts#L414

This should allow wildcard domain or propertyId as it is supported by API: https://techdocs.akamai.com/edgeworkers/reference/post-secure-token

@guillaume-fr guillaume-fr linked a pull request Mar 14, 2022 that will close this issue
@bmatthew
Copy link
Collaborator

bmatthew commented Mar 21, 2022

Hey @guillaume-fr -- thanks for raising this ticket and the PR. Sorry for the late reply here, I was away last week, but I have some info from an engineer on our team who looked into this problem.

Unfortunately this is not something that can be fixed with a CLI change alone. The EW CLI is dependent on calls out to the Akamai OPEN API -- in this case the Edge Secret Store API and components associated with it have an issue where they do not properly handle wildcard domains. We are starting work on an overhaul to this API which should be finished & deployed in the next few months.

I'll leave this ticket open until we have a chance to ensure the new API + the CLI command here works with wildcard domains.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants