Update users.md by MichaelJCole · Pull Request #801 · parse-community/docs

MichaelJCole · 2020-12-02T19:20:26Z

Hi, this is based on my experience attempting to use the Parse GraphQL API with a custom Quasar front-end from this guide. I'm using the "customPages" feature which may be different from other users. Parse seems to be a great back-end data provider, and I'm excited to start building features with it!

See also: parse-community/parse-server#7033 and parse-community/parse-server#7028

The REST Guide might benefit from the same documentation. I'm very new to Parse, so edits welcome.
Thank you

Hi, this is based on my experience attempting to use the Parse GraphQL API with a custom Quasar front-end from this guide. I'm using the "customPages" feature which may be different from other users. Parse seems to be a great back-end data provider, and I'm excited to start building features with it! See also: parse-community/parse-server#7033 and parse-community/parse-server#7028 The REST Guide might benefit from the same documentation. Thank you

_includes/graphql/users.md

TomWFox

Thanks for the PR!

TomWFox · 2021-01-26T18:10:41Z

_includes/graphql/users.md

 }
 ```
+
+The emailed verification link will GET the Parse REST API to verify the token is still valid.  For example:


Suggested change

The emailed verification link will GET the Parse REST API to verify the token is still valid. For example:

The emailed verification link will GET the Parse REST API to verify the token is still valid. For example:

TomWFox · 2021-01-26T18:10:55Z

_includes/graphql/users.md

+
+Parse will then process the token and forward the user's browser to verified or invalid page provided by the Parse server itself.
+
+Optionally, the Parse server can be configured to forward to custom pages with-in your web application: `verifyEmailSuccess` or `customPages.invalidLink`.  Please see the "Resetting Passwords" section for an example and links to further documentation.


Can you also add a link for resetting passwords...

Suggested change

Optionally, the Parse server can be configured to forward to custom pages with-in your web application: `verifyEmailSuccess` or `customPages.invalidLink`. Please see the "Resetting Passwords" section for an example and links to further documentation.

Optionally, the Parse Server can be configured to forward to custom pages within your web application: `verifyEmailSuccess` or `customPages.invalidLink`. Please see the "Resetting Passwords" section for further documentation.

TomWFox · 2021-01-26T18:11:11Z

_includes/graphql/users.md

-The verification email is automatically sent on sign up; this mutation is useful if the user didn't receive the first email. Again, an email adapter must be configured for this mutation to work.
+To use the `sendVerificationEmail` mutation your Parse Server must have an [email adapter configured as described in the Parse Server guide](https://docs.parseplatform.org/parse-server/guide/#welcome-emails-and-email-verification).
+
+When configured, Parse server will automatically send emails on sign up.  this mutation will re-send an email with a password reset link if the user didn't receive the first email or the token expired.


Suggested change

When configured, Parse server will automatically send emails on sign up. this mutation will re-send an email with a password reset link if the user didn't receive the first email or the token expired.

When configured, Parse server will automatically send emails on sign up. This mutation will re-send an email with a password reset link if the user didn't receive the first email or the token expired.

TomWFox · 2021-01-26T18:12:20Z

_includes/graphql/users.md

+
+```
+
+The Parse server forwards the browser to: `choosePassword: \`${process.env.APP_PUBLIC_URL}/auth/reset-password\`,` where your web application accepts the user's new password, and crafts a response to the server.  For example, using the $axios http library.


Suggested change

The Parse server forwards the browser to: `choosePassword: \`${process.env.APP_PUBLIC_URL}/auth/reset-password\`,` where your web application accepts the user's new password, and crafts a response to the server. For example, using the $axios http library.

The Parse Server forwards the browser to `${process.env.APP_PUBLIC_URL}/auth/reset-password`, where your web application accepts the user's new password, and crafts a response to the server. For example, using the $axios http library.

TomWFox · 2021-01-26T18:13:12Z

_includes/graphql/users.md

+```
+Parse will then forward the user's browser to a password reset page provided (or invalid token page) by the Parse server itself.
+
+Optionally, the Parse server can be configured to forward to a custom page with-in your web application.  This is done using the ["customPages" feature](https://parseplatform.org/parse-server/api/master/CustomPagesOptions.html).  For example, using Express:


Suggested change

Optionally, the Parse server can be configured to forward to a custom page with-in your web application. This is done using the ["customPages" feature](https://parseplatform.org/parse-server/api/master/CustomPagesOptions.html). For example, using Express:

Optionally, the Parse server can be configured to forward to a custom page with-in your web application. This is done using the ["customPages" feature](https://parseplatform.org/parse-server/api/master/CustomPagesOptions.html). For example, using Express:

TomWFox · 2021-01-26T18:13:25Z

_includes/graphql/users.md

 }
 ```

+The emailed password reset link will GET the Parse REST API to verify the token is still valid.  For example:


Suggested change

The emailed password reset link will GET the Parse REST API to verify the token is still valid. For example:

The emailed password reset link will GET the Parse REST API to verify the token is still valid. For example:

TomWFox · 2021-01-26T18:20:30Z

_includes/graphql/users.md

+https://www.example.com/parse/apps/APP_ID/verify_email?token=xxxxxxxxxxxx&username=test%4example.com
+```
+
+Parse will then process the token and forward the user's browser to verified or invalid page provided by the Parse server itself.


Suggested change

Parse will then process the token and forward the user's browser to verified or invalid page provided by the Parse server itself.

Parse will then process the token and forward the user's browser to verified or invalid page provided by the Parse Server itself.

TomWFox · 2021-01-26T18:33:01Z

_includes/graphql/users.md

+```
+const parseServer = new ParseServer({
+  // Basics: https://github.com/parse-community/parse-server#basic-options
+   appId: process.env.PARSE_SERVER_APPLICATION_ID,
+  ...otherOptions
+
+  // Email: https://github.com/parse-community/parse-server#email-verification-and-password-reset
+  verifyUserEmails: true,
+  emailVerifyTokenValidityDuration: 2 * weekInSeconds,
+  preventLoginWithUnverifiedEmail: false,
+
+  // Emailed links point to this host.  It must include `/parse`
+  publicServerURL: process.env.PARSE_PUBLIC_SERVER_URL || process.env.PARSE_SERVER_URL,
+  // Your apps name. This will appear in the subject and body of the emails that are sent.
+  appName: 'Application Name for User',
+  // The email adapter
+  emailAdapter: {
+    module: "parse-server-aws-ses",
+    options: {
+      from: `Hello <${process.env.EMAIL_FROM_ADDRESS}>`,
+      region: process.env.AWS_REGION,
+      // aws-sdk loads keys from environment variables
+    }
+  },


Can you remove/comment the non-code text - ...otherOptions etc

mtrezza · 2021-07-26T20:27:22Z

@MichaelJCole It's been some time, but it would be great if you were still available to help make these changes. Do you have any questions regarding the review?

davimacedo reviewed Dec 2, 2020

View reviewed changes

_includes/graphql/users.md Show resolved Hide resolved

TomWFox requested a review from mtrezza December 15, 2020 15:05

TomWFox suggested changes Jan 26, 2021

View reviewed changes

mtrezza removed their request for review July 26, 2021 20:27

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update users.md#801

Update users.md#801
MichaelJCole wants to merge 1 commit intoparse-community:gh-pagesfrom
MichaelJCole:patch-2

MichaelJCole commented Dec 2, 2020

Uh oh!

Uh oh!

TomWFox left a comment

Uh oh!

TomWFox Jan 26, 2021

Uh oh!

TomWFox Jan 26, 2021

Uh oh!

TomWFox Jan 26, 2021

Uh oh!

TomWFox Jan 26, 2021

Uh oh!

TomWFox Jan 26, 2021

Uh oh!

TomWFox Jan 26, 2021

Uh oh!

TomWFox Jan 26, 2021

Uh oh!

TomWFox Jan 26, 2021

Uh oh!

mtrezza commented Jul 26, 2021

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

	The emailed verification link will GET the Parse REST API to verify the token is still valid. For example:
	The emailed verification link will GET the Parse REST API to verify the token is still valid. For example:


		Parse will then process the token and forward the user's browser to verified or invalid page provided by the Parse server itself.

		Optionally, the Parse server can be configured to forward to custom pages with-in your web application: `verifyEmailSuccess` or `customPages.invalidLink`. Please see the "Resetting Passwords" section for an example and links to further documentation.

	When configured, Parse server will automatically send emails on sign up. this mutation will re-send an email with a password reset link if the user didn't receive the first email or the token expired.
	When configured, Parse server will automatically send emails on sign up. This mutation will re-send an email with a password reset link if the user didn't receive the first email or the token expired.


		```

		The Parse server forwards the browser to: `choosePassword: \`${process.env.APP_PUBLIC_URL}/auth/reset-password\`,` where your web application accepts the user's new password, and crafts a response to the server. For example, using the $axios http library.

	The emailed password reset link will GET the Parse REST API to verify the token is still valid. For example:
	The emailed password reset link will GET the Parse REST API to verify the token is still valid. For example:

Uh oh!

Conversation

MichaelJCole commented Dec 2, 2020

Uh oh!

Uh oh!

TomWFox left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mtrezza commented Jul 26, 2021

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants