Hi Anju,

It's not clear if you're asking about Verify SaaS or Verify Access.

For Verify Access I don't know the answer.  I don't think the consent date is saved.

For Verify SaaS, consent date information is saved if you are using the new Data Privacy and Consent Management component.  When using this, OAuth scope consents are saved within the consent management framework which means you can see the consent dates in the console and also should be possible to pull them out with REST API if you want to show to user.  If you set up an OIDC application before DPCM was available, there is an option in the UI which allows migration to DPCM.

Jon.

Hi Anju,

Security Verify Access does not store the date the consent was given.  The associated tables in the HVDB are:

COPY public.oauth_trusted_client (trusted_client_id, username, client_id) FROM stdin;
532a54fd-edc6-407a-9783-6c7f172ffce2 iuser my_client_id

--
-- Data for Name: oauth_scope; Type: TABLE DATA; Schema: public; Owner: www-data
--
COPY public.oauth_scope (trusted_client_id, scope) FROM stdin;
532a54fd-edc6-407a-9783-6c7f172ffce2 openid
532a54fd-edc6-407a-9783-6c7f172ffce2 ScopeA

These are populated when "Prompt once and remember" is used.

Hi Anju,

Security Verify Access does not store the date the consent was given.  The associated tables in the HVDB are:

COPY public.oauth_trusted_client (trusted_client_id, username, client_id) FROM stdin;
532a54fd-edc6-407a-9783-6c7f172ffce2 iuser my_client_id

--
-- Data for Name: oauth_scope; Type: TABLE DATA; Schema: public; Owner: www-data
--
COPY public.oauth_scope (trusted_client_id, scope) FROM stdin;
532a54fd-edc6-407a-9783-6c7f172ffce2 openid
532a54fd-edc6-407a-9783-6c7f172ffce2 ScopeA

These are populated when "Prompt once and remember" is used.