API Credential Keys

Liberty Create - Build Advice
1

Is there any way of exposing the API keys outside of Build Studio ?

We are looking now at a client requirement for rolling API keys - i.e. having a new one generated every xx days or so.

At the moment the handling of this would be painful and entirely manual on both sides. which is far from ideal.

Viewing the keys (for the environment) in the scope of the running application I guess would be the bare minimum but the option to trigger regeneration of the keys etc could be quite useful - particularly if exposed by rule capability then it could be triggered on a schedule and other clever things could be done.

Thanks

Haydn

2

Sorry I should have said, that this is for INBOUND requests - so calling of API functions.

3

Hi Haydn,

With generic you can set to use a custom authentication processor which would allow for you to accept a token within the header and use your custom code to handle it. In this way you could easily set up a rolling key which you could store in either an object or a variable which the processor would authenticate against.

Let me know if you need any further assistance.

4

Adam,

Yes I figured it would probably have to be a generic function if it was possible at all.

It complicates things from configuring the respective payloads but I guess those could be resolved. For example the whole “inline” thing vs property values.

If and when I get to this - I may well reach out for some advice.

Thanks

Haydn