I'm trying to create an API to be called by another application but it needs security to be enabled and the current GetKey implementation that functions like a user session adds unnecessary complexity. There doesn't seem to be a good reason for the key to expire in this scenario as the credentials would need to be hardcoded anyway, and this just adds another layer of complexity to worry about.
Is there a way to generate a key for authenticated APIs created through the IDE that doesn't expire?
Persistent API Key
-
- Posts: 178
- Joined: August 31st, 2021, 11:37 am
- Contact:
Persistent API Key
word count: 90
-
- Posts: 88
- Joined: August 26th, 2021, 5:21 pm
- Contact:
Re: Persistent API Key
Our current REST Implementation is based on user based authentication (token). You provide user/pwd and we give you a token that is valid for that session and can be used to authenticate in the same session,
Based on your suggestions, we will look into possibility of a site based authentication. From IDE, you will generate a Key using a unique site name. You can then use this key to call REST API directly without using GetKey REST API.
Based on your suggestions, we will look into possibility of a site based authentication. From IDE, you will generate a Key using a unique site name. You can then use this key to call REST API directly without using GetKey REST API.
word count: 79
-
- Posts: 88
- Joined: August 26th, 2021, 5:21 pm
- Contact: