Update: Oxygen Key Scope


The Oxygen team just added a feature that allows *.autodeskplm360.net as the scope on a Consumer Key.  Previously you couldn’t have a wildcard in the front, which meant your key would only work on a specific PLM 360 tenant.

Now you can use the *.autodeskplm360.net scope to write apps that work with all PLM 360 tenants.  Of course, you can still scope things to a specific tenant if you want.  A narrow scope is useful for things like in-house utilities and consulting projects.

If you already have an Oxygen key, you can get the scope changed.  Just make another key request and indicate that you want the scope updated on your existing key.  Make sure to include your public Consumer Key in the request.



Comments

Leave a Reply

Discover more from Autodesk Developer Blog

Subscribe now to keep reading and get access to the full archive.

Continue reading