Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos #55

Closed
wants to merge 1 commit into from
Closed

Fix typos #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions registry/Onboarding of Participants.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@
</body>
</html>
```
> *Note: Please use the illustrated html as-is and only replace `SIGNED_UNIQUE_REQ_ID` with your correspnding generated signature, specifically use single quotes `'` to hold the information*
> *Note: Please use the illustrated html as-is and only replace `SIGNED_UNIQUE_REQ_ID` with your corresponding generated signature, specifically use single quotes `'` to hold the information*

12. Configure developed /on_subscribe implementation to use enc_dec_private_key (generated in step 8) and ONDC public key to decrypt the challenge_string
13. Create /subscribe request as follows
Expand Down Expand Up @@ -187,7 +187,7 @@ Please connect with ONDC officials - Supriyo and Neeraj and get your subscriber
}
```
Resolution
Need to put timestamp within stipulated timegap defined by ONDC.
Need to put timestamp within stipulated time gap defined by ONDC.
### Domain Verification Failed
```
{
Expand Down Expand Up @@ -304,5 +304,5 @@ Resolution
Resolution
- Use Plain Request_ID: Network Participant should use plain request_id while generating signature, without applying any hashing on the request_id
- Ensure Consistent Request_ID: Network Participant should use the same request_id in request body which they used while generating the signature. The request_id used during signature generation must match the one used during verification to ensure successful validation
- Ensure signing public key: Network Participant should send the same signing public key in the request body, who's corresnponding signing private key was used for signing.
- Ensure signing public key: Network Participant should send the same signing public key in the request body, who's corresponding signing private key was used for signing.