The default authorization server is a preconfigured custom authorization that comes with the API AM license.
If you will need to be able to remotely validate access tokens with your own APIs you should reach out to your Okta Account Executive to have API AM enabled.
@erik That was an example to the ISSUER that I gave.My actual issuer is different and I am able to see all the APIs listed in json format when I go to the below URL.
Can you double check that the issuer and client ID you’re providing to the verifier are correct? The issuer URL for the custom authorization server you are using can be found at Security → API → Authorization Servers → {{the authorization server you are using}} → Issuer URI and the Client ID is found at Applications → {{the application you are using}} → General → Client ID
Make sure that the Issuer you set here is the same as the one used by your front end app! You can check what issuer the front end app is using by decoding the token (using token.dev or jwt.io) and looking at the iss value.