Hi. I have some questions.
A customer asked about the driving logic of the internal certification. Is there a way to know more information than document?
And, Which table does 'Look Up API Key' assertion use?
Please solve my question. Thank you.
Would you be able to clarify what you are asking for "driving logic of the internal certification" as I'm not certain I understand the question. As for the Look Up API Key assertion, it looks at the OTK database portal_apikey table.
Thank you for reply.
It's translation mistake.
I wanted to say how internal assertion works.
And if 'look up api key' use otk db, oauth module is necessary for it?
I thought it is different from 'portal look up api key', isn't it?
Good afternoon. The API Portal v3.5 integration comes with an assertion called 'Look Up API Key'. This assertion is used wherever an API should only be accessible for certain API keys. For the integration OTK will provide an encapsulated assertion named 'Portal Look Up API Key' to set the same variables as the current assertion does. This assertion will either retrieve the API Key from a local database via Portal Look Up API Key DB or via the API GET /portal/storage?apikey=value