Content key is not shown

[mc0re]

Please provide us with the following information:

This issue concerns: (mark with an x)

- [ ] AMSE v4.x (for AMS v2)
- [x] AMSE v5.x (for AMS v3)

This issue is for a: (mark with an x)

- [x] bug report
- [ ] UI issue report
- [ ] feature request
- [ ] performance problem
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I had an Azure account with a media service account. I deleted it, then created a new one with the same name. Created a new empty asset in it. The streaming point is not turned on.
Opening AMSE shows that single asset and no keys attached.
Using IAzureMediaServicesClient.StreamingLocators.CreateAsync() with the key ID I had previously (and should've been deleted) yields an error:

Content key id '95045bfd-3cf0-489b-8871-381fdc87e27a' already exists, please choose another one.

So there is a key somewhere, but AMSE does not show it.

Any log messages given by the failure

AMSE yields no errors.

Expected/desired behavior

AMSE shows the hidden key.

OS and Version?

Windows 10.

Versions

AMSE 5.2.0.4 for Media Services v3

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

[xpouyat]

Hello,
Do you think it's an issue with AMSE, or with Azure Media Services API ? If the latter, you should open a support ticket in the Azure portal.

[mc0re]

I wouldn't know. The key is not shown, I haven't tried going through the API to look for it...

[xpouyat]

Can you describe better the repro steps ? Because you say that you create an empty asset with AMSE, but it looks like you are calling the API too.

[mc0re]

I created a media account and an asset on the portal - didn't know one can modify the data in AMSE :-) Then created a key using the API, encrypted a file, etc. Then deleted the account completely to clean up (portal). Created a new account with the same name (portal). Created an asset (portal).
Checked with AMSE - all clean, one asset, no keys.
Tried to create a key with API - error.
So as I see it, the key still exists somewhere, but is not visible in AMSE. It could be an API or portal error, I can't really know. For me the entry point was AMSE :-)