Skip to main content
Para provides a comprehensive set of methods for managing authentication sessions in Flutter applications. These sessions are crucial for secure transaction signing and other authenticated operations.

Session Duration

Para session length is configured per API key and can be set up to 30 days through the Configuration section of the or CLI. The Para API enforces the configured duration. Signing a message or transaction, or calling the session keep-alive method, can extend an active session according to that configuration.

Managing Sessions

Checking Session Status

Use isSessionActive() to verify whether a user’s session is currently valid before performing authenticated operations.
In Flutter applications, it’s especially important to check the session status before allowing users to access authenticated areas of your app due to the persistence of local storage between app launches.
Example usage:

Refreshing Expired Sessions

When a session has expired, Para recommends initiating a full authentication flow rather than trying to refresh the session.
For Flutter applications, always call logout() before reinitiating authentication when a session has expired to ensure all stored data is properly cleared.

Exporting Sessions to Your Server

Use exportSession() when you need to transfer session state to your server for performing operations on behalf of the user.
Example implementation:

Best Practices for Flutter

  1. Check Sessions on App Launch: Verify session status when your app starts to determine if users need to reauthenticate.
  1. Handle App Lifecycle Changes: Flutter apps can be backgrounded and foregrounded, which may affect session status.

Next Steps

Explore more advanced features and integrations with Para in Flutter: