Secure resource access
There are three types of authentication tokens your app can use to securely access resources like account information, transactions, and so on from a back-end or resource server. A user or device needs to be authenticated before a resource can be fetched with the corresponding authentication token. Different resources might require using different methods for authentication. The following authentication token types can be used:
- User authentication (default): Requires the user to be authenticated, meaning to be authenticated with an authenticator (PIN or fingerprint for example).
- Implicit authentication: Requires the user to be implicitly authenticated, meaning the user has registered with the device before. This does not require interaction with an authenticator like PIN or fingerprint.
- Anonymous authentication: Requires the device to be registered and authenticated with the IDAAS-core, but no user has to be authenticated in any way.
Additionally, we support unauthenticated resource requests, which do not require an access token but instead only apply certificate pinning.
The Flutter Plugin exposes the resourceRequest method to perform these different types of resource requests. The plugin ensures the confidentiality and authenticity of the payload. The application itself is responsible for the structure or processing of the payload.
Enabling additional resource base URLs for requests
When configuring the IDAAS-core, you can set a resource base URL that will be used as an allow-list for making resource requests. However, it is possible to allow additional resource URLs as long as the certificates for these URLs are added within the IDAAS-core configuration.
To enable this functionality, an additional step is required where the base of the resource URLs are added during the app initialization when calling the startApplication function.
Configure resource request
The request can be configured by passing a RequestDetails object to the function. This will allow you to set the:
- Url Path: The Path can be relative to the resource base URL defined in the IDAAS-core configuration or be an absolute URL.
- Type of http request (GET, POST, DELETE, PUT)
- Optional headers
- Optional body
Resource request response
The request will then respond with a RequestResponse object.
Using fetch with user authentication
To successfully request a resource for a specific user, the client credentials must be valid and the user must have a valid access token. In other words, the user must be logged in before a resource call can be made on their behalf. This type of resource request should be used to fetch sensitive data that requires user authentication, like account details and transaction history. After user authentication a resource can be fetched as follows:
Using fetch with implicit authentication
Before fetching an implicit resource, the user must first be authenticated implicitly.
Using fetch with anonymous authentication
A device can use its OAuth credentials to authenticate itself with the IDAAS-core and obtain an access token. An anonymous resource call can be used in cases where a user does not need to be logged in or even registered in order to use certain functionality, or access some resource.
Using fetch unauthenticated
Unauthenticated resource requests that will only use certificate pinning can be performed through:
