Skip to content

Commit 92d63e9

Browse files
Neno StefanovNenoStefanov
authored andcommitted
Add more reference links in the README
1 parent 01fed26 commit 92d63e9

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

README.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -126,20 +126,22 @@ offers two options for that:
126126
- If the end user is registering for the first time or resetting their PIN,
127127
an email with a verification code will be sent, and the email
128128
verification method in the response will be
129-
`EmailVerificationMethod.code`.
129+
[EmailVerificationMethod.code](https://pub.dev/documentation/flutter_miracl_sdk/latest/flutter_miracl_sdk/EmailVerificationMethod.html#code).
130130
Then, ask the user to enter the code in the application.
131131

132132
- If the end user has already registered another device with the same
133133
User ID, a Verification URL will be sent, and the verification method in
134134
the response will be
135-
`EmailVerificationMethod.link`.
135+
[EmailVerificationMethod.link](https://pub.dev/documentation/flutter_miracl_sdk/latest/flutter_miracl_sdk/EmailVerificationMethod.html#link).
136136
In this case, proceed as described for the **Email Link** verification
137137
method below.
138138

139139
- **Email Link:** Your application must open when the end user follows
140140
the Verification URL in the email. To ensure proper deep linking behaviour
141141
on mobile applications, check this [guide](https://docs.flutter.dev/ui/navigation/deep-linking)
142-
package.
142+
package. To associate your application with the email Verification URL, use
143+
the **Android association** field in **Mobile Applications** under
144+
**Configuration** in the [MIRACL Trust Portal](https://trust.miracl.cloud).
143145

144146
### Registration
145147

@@ -212,7 +214,7 @@ The MIRACL Trust SDK offers two options:
212214

213215
The
214216
[authenticate](https://pub.dev/documentation/flutter_miracl_sdk/latest/flutter_miracl_sdk/MIRACLTrust/authenticate.html)
215-
method generates a [JWT](https://jwt.io) authentication
217+
method generates a [JWT](https://datatracker.ietf.org/doc/html/rfc7519) authentication
216218
token for а registered user.
217219

218220
```dart
@@ -310,8 +312,8 @@ entry in the response body indicates that the signing is successful.
310312
[QuickCode](https://miracl.com/resources/docs/guides/built-in-user-verification/quickcode/)
311313
is a way to register another device without going through the verification process.
312314

313-
To generate a QuickCode, call the
314-
[generateQuickCode](https://pub.dev/documentation/flutter_miracl_sdk/latest/flutter_miracl_sdk/MIRACLTrust/generateQuickCode.html)
315+
To generate a [QuickCode](https://pub.dev/documentation/flutter_miracl_sdk/latest/flutter_miracl_sdk/QuickCode-class.html),
316+
call the [generateQuickCode](https://pub.dev/documentation/flutter_miracl_sdk/latest/flutter_miracl_sdk/MIRACLTrust/generateQuickCode.html)
315317
method with
316318
an already registered
317319
[User](https://pub.dev/documentation/flutter_miracl_sdk/latest/flutter_miracl_sdk/User-class.html)

0 commit comments

Comments
 (0)