parse-server 9.2.0 → 9.2.1-alpha.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/lib/Auth.js +26 -2
- package/lib/Controllers/PushController.js +2 -2
- package/lib/Routers/PagesRouter.js +12 -10
- package/package.json +3 -3
- package/public/custom_json.html +17 -0
- package/public/custom_json.json +23 -0
- package/public/custom_page.html +15 -0
- package/public/de/email_verification_link_expired.html +24 -0
- package/public/de/email_verification_link_invalid.html +21 -0
- package/public/de/email_verification_send_fail.html +21 -0
- package/public/de/email_verification_send_success.html +19 -0
- package/public/de/email_verification_success.html +18 -0
- package/public/de/password_reset.html +65 -0
- package/public/de/password_reset_link_invalid.html +19 -0
- package/public/de/password_reset_success.html +18 -0
- package/public/de-AT/email_verification_link_expired.html +24 -0
- package/public/de-AT/email_verification_link_invalid.html +21 -0
- package/public/de-AT/email_verification_send_fail.html +21 -0
- package/public/de-AT/email_verification_send_success.html +19 -0
- package/public/de-AT/email_verification_success.html +18 -0
- package/public/de-AT/password_reset.html +65 -0
- package/public/de-AT/password_reset_link_invalid.html +19 -0
- package/public/de-AT/password_reset_success.html +18 -0
- package/public/email_verification_link_expired.html +24 -0
- package/public/email_verification_link_invalid.html +21 -0
- package/public/email_verification_send_fail.html +21 -0
- package/public/email_verification_send_success.html +19 -0
- package/public/email_verification_success.html +18 -0
- package/public/password_reset.html +65 -0
- package/public/password_reset_link_invalid.html +19 -0
- package/public/password_reset_success.html +18 -0
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a verify email link with a security
|
|
4
|
+
token that is expired or incorrect. This can either mean the user has clicked
|
|
5
|
+
on a stale link (i.e. re-clicked on the link) or this could be a sign of a
|
|
6
|
+
malicious user trying to tamper with your app.
|
|
7
|
+
-->
|
|
8
|
+
<html>
|
|
9
|
+
|
|
10
|
+
<head>
|
|
11
|
+
<title>Email Verification</title>
|
|
12
|
+
</head>
|
|
13
|
+
|
|
14
|
+
<body>
|
|
15
|
+
<h1>{{appName}}</h1>
|
|
16
|
+
<h1>Expired verification link!</h1>
|
|
17
|
+
<form method="POST" action="{{publicServerUrl}}/apps/{{appId}}/resend_verification_email">
|
|
18
|
+
<input name="token" type="hidden" value="{{token}}">
|
|
19
|
+
<input name="locale" type="hidden" value="{{locale}}">
|
|
20
|
+
<button type="submit">Resend Link</button>
|
|
21
|
+
</form>
|
|
22
|
+
</body>
|
|
23
|
+
|
|
24
|
+
</html>
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a verify email link with parameters
|
|
4
|
+
that are missing or incorrect. This can either mean the user has incorrectly
|
|
5
|
+
entered a link or this could be a sign of a malicious user trying to tamper
|
|
6
|
+
with your app.
|
|
7
|
+
If the link contains an expired security token (or the email has already
|
|
8
|
+
been verified), this page is not displayed, there is another page for that.
|
|
9
|
+
-->
|
|
10
|
+
<html>
|
|
11
|
+
|
|
12
|
+
<head>
|
|
13
|
+
<title>Email Verification</title>
|
|
14
|
+
</head>
|
|
15
|
+
|
|
16
|
+
<body>
|
|
17
|
+
<h1>{{appName}}</h1>
|
|
18
|
+
<h1>Invalid verification link!</h1>
|
|
19
|
+
</body>
|
|
20
|
+
|
|
21
|
+
</html>
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a verify email link with a security
|
|
4
|
+
token that is expired or incorrect, then requests to receive another link,
|
|
5
|
+
but it fails because the username is invalid or the email has already been
|
|
6
|
+
verified. This can either mean the user has previously verified the email
|
|
7
|
+
or this could be a sign of a malicious user trying to tamper with your app.
|
|
8
|
+
-->
|
|
9
|
+
<html>
|
|
10
|
+
|
|
11
|
+
<head>
|
|
12
|
+
<title>Email Verification</title>
|
|
13
|
+
</head>
|
|
14
|
+
|
|
15
|
+
<body>
|
|
16
|
+
<h1>{{appName}}</h1>
|
|
17
|
+
<h1>Invalid link!</h1>
|
|
18
|
+
<p>No link sent. User not found or email already verified.</p>
|
|
19
|
+
</body>
|
|
20
|
+
|
|
21
|
+
</html>
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a verify email link with a
|
|
4
|
+
security token that is expired, then requests to receive another email
|
|
5
|
+
with a new link and the email is sent successfully.
|
|
6
|
+
-->
|
|
7
|
+
<html>
|
|
8
|
+
|
|
9
|
+
<head>
|
|
10
|
+
<title>Email Verification</title>
|
|
11
|
+
</head>
|
|
12
|
+
|
|
13
|
+
<body>
|
|
14
|
+
<h1>{{appName}}</h1>
|
|
15
|
+
<h1>Link sent!</h1>
|
|
16
|
+
<p>A new link has been sent. Check your email.</p>
|
|
17
|
+
</body>
|
|
18
|
+
|
|
19
|
+
</html>
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a verify email link and the
|
|
4
|
+
email gets verified successfully.
|
|
5
|
+
-->
|
|
6
|
+
<html>
|
|
7
|
+
|
|
8
|
+
<head>
|
|
9
|
+
<title>Email Verification</title>
|
|
10
|
+
</head>
|
|
11
|
+
|
|
12
|
+
<body>
|
|
13
|
+
<h1>{{appName}}</h1>
|
|
14
|
+
<h1>Email verified!</h1>
|
|
15
|
+
<p>Successfully verified your email for account: {{username}}.</p>
|
|
16
|
+
</body>
|
|
17
|
+
|
|
18
|
+
</html>
|
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when someone clicks a valid 'reset password' link.
|
|
4
|
+
Users should feel free to add to this page (i.e. branding or security widgets)
|
|
5
|
+
but should be sure not to delete any of the form inputs or the javascript from the
|
|
6
|
+
template file. This javascript is what adds the necessary values to authenticate
|
|
7
|
+
this session with Parse.
|
|
8
|
+
The query params 'username' and 'app' hold the friendly names for your current user and
|
|
9
|
+
your app. You should feel free to incorporate their values to make the page more personal.
|
|
10
|
+
If you are missing form parameters in your POST, Parse will navigate back to this page and
|
|
11
|
+
add an 'error' query parameter.
|
|
12
|
+
-->
|
|
13
|
+
<html>
|
|
14
|
+
|
|
15
|
+
<head>
|
|
16
|
+
<title>Password Reset</title>
|
|
17
|
+
</head>
|
|
18
|
+
|
|
19
|
+
<body>
|
|
20
|
+
<h1>{{appName}}</h1>
|
|
21
|
+
<h1>Reset Your Password</h1>
|
|
22
|
+
<noscript><p>We apologize, but resetting your password requires javascript</p></noscript>
|
|
23
|
+
<p>You can set a new Password for your account: {{username}}</p>
|
|
24
|
+
<br />
|
|
25
|
+
<p>{{error}}</p>
|
|
26
|
+
<form id='form' action='{{publicServerUrl}}/apps/{{appId}}/request_password_reset' method='POST'>
|
|
27
|
+
<input name='utf-8' type='hidden' value='✓' />
|
|
28
|
+
<input name="username" type="hidden" id="username" value="{{username}}" />
|
|
29
|
+
<input name="token" type="hidden" id="token" value="{{token}}" />
|
|
30
|
+
<input name="locale" type="hidden" id="locale" value="{{locale}}" />
|
|
31
|
+
|
|
32
|
+
<p>New Password</p>
|
|
33
|
+
<input name="new_password" type="password" id="password" />
|
|
34
|
+
<p>Confirm New Password</p>
|
|
35
|
+
<input name="confirm_new_password" type="password" id="password_confirm" />
|
|
36
|
+
<br />
|
|
37
|
+
<p id="password_match_info"></p>
|
|
38
|
+
<br />
|
|
39
|
+
<button id="change_password">Change Password</button>
|
|
40
|
+
</form>
|
|
41
|
+
|
|
42
|
+
<script>
|
|
43
|
+
window.onload = function() {
|
|
44
|
+
document.getElementById("password").oninput = validatePassword;
|
|
45
|
+
document.getElementById("password_confirm").oninput = validatePassword;
|
|
46
|
+
document.getElementById("change_password").disabled = true;
|
|
47
|
+
|
|
48
|
+
function validatePassword() {
|
|
49
|
+
var pass2 = document.getElementById("password").value;
|
|
50
|
+
var pass1 = document.getElementById("password_confirm").value;
|
|
51
|
+
if(pass1 !== pass2) {
|
|
52
|
+
if(document.getElementById("password_confirm").value) {
|
|
53
|
+
document.getElementById("change_password").disabled = true;
|
|
54
|
+
document.getElementById("password_match_info").innerHTML = "Must match the previous entry";
|
|
55
|
+
}
|
|
56
|
+
} else {
|
|
57
|
+
document.getElementById("change_password").disabled = false;
|
|
58
|
+
document.getElementById("password_match_info").innerHTML = "";
|
|
59
|
+
}
|
|
60
|
+
}
|
|
61
|
+
}
|
|
62
|
+
</script>
|
|
63
|
+
</body>
|
|
64
|
+
|
|
65
|
+
</html>
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a password reset link with parameters
|
|
4
|
+
that are missing or incorrect. This can either mean the user has incorrectly
|
|
5
|
+
entered a link or this could be a sign of a malicious user trying to tamper
|
|
6
|
+
with your app.
|
|
7
|
+
-->
|
|
8
|
+
<html>
|
|
9
|
+
|
|
10
|
+
<head>
|
|
11
|
+
<title>Password Reset</title>
|
|
12
|
+
</head>
|
|
13
|
+
|
|
14
|
+
<body>
|
|
15
|
+
<h1>{{appName}}</h1>
|
|
16
|
+
<h1>Invalid password reset link!</h1>
|
|
17
|
+
</body>
|
|
18
|
+
|
|
19
|
+
</html>
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a reset password link, then submits
|
|
4
|
+
the form with a new password and the password gets updated successfully.
|
|
5
|
+
-->
|
|
6
|
+
<html>
|
|
7
|
+
|
|
8
|
+
<head>
|
|
9
|
+
<title>Password Reset</title>
|
|
10
|
+
</head>
|
|
11
|
+
|
|
12
|
+
<body>
|
|
13
|
+
<h1>{{appName}}</h1>
|
|
14
|
+
<h1>Success!</h1>
|
|
15
|
+
<p>Your password has been updated.</p>
|
|
16
|
+
</body>
|
|
17
|
+
|
|
18
|
+
</html>
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a verify email link with a security
|
|
4
|
+
token that is expired or incorrect. This can either mean the user has clicked
|
|
5
|
+
on a stale link (i.e. re-clicked on the link) or this could be a sign of a
|
|
6
|
+
malicious user trying to tamper with your app.
|
|
7
|
+
-->
|
|
8
|
+
<html>
|
|
9
|
+
|
|
10
|
+
<head>
|
|
11
|
+
<title>Email Verification</title>
|
|
12
|
+
</head>
|
|
13
|
+
|
|
14
|
+
<body>
|
|
15
|
+
<h1>{{appName}}</h1>
|
|
16
|
+
<h1>Expired verification link!</h1>
|
|
17
|
+
<form method="POST" action="{{publicServerUrl}}/apps/{{appId}}/resend_verification_email">
|
|
18
|
+
<input name="token" type="hidden" value="{{token}}">
|
|
19
|
+
<input name="locale" type="hidden" value="{{locale}}">
|
|
20
|
+
<button type="submit">Resend Link</button>
|
|
21
|
+
</form>
|
|
22
|
+
</body>
|
|
23
|
+
|
|
24
|
+
</html>
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a verify email link with parameters
|
|
4
|
+
that are missing or incorrect. This can either mean the user has incorrectly
|
|
5
|
+
entered a link or this could be a sign of a malicious user trying to tamper
|
|
6
|
+
with your app.
|
|
7
|
+
If the link contains an expired security token (or the email has already
|
|
8
|
+
been verified), this page is not displayed, there is another page for that.
|
|
9
|
+
-->
|
|
10
|
+
<html>
|
|
11
|
+
|
|
12
|
+
<head>
|
|
13
|
+
<title>Email Verification</title>
|
|
14
|
+
</head>
|
|
15
|
+
|
|
16
|
+
<body>
|
|
17
|
+
<h1>{{appName}}</h1>
|
|
18
|
+
<h1>Invalid verification link!</h1>
|
|
19
|
+
</body>
|
|
20
|
+
|
|
21
|
+
</html>
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a verify email link with a security
|
|
4
|
+
token that is expired or incorrect, then requests to receive another link,
|
|
5
|
+
but it fails because the username is invalid or the email has already been
|
|
6
|
+
verified. This can either mean the user has previously verified the email
|
|
7
|
+
or this could be a sign of a malicious user trying to tamper with your app.
|
|
8
|
+
-->
|
|
9
|
+
<html>
|
|
10
|
+
|
|
11
|
+
<head>
|
|
12
|
+
<title>Email Verification</title>
|
|
13
|
+
</head>
|
|
14
|
+
|
|
15
|
+
<body>
|
|
16
|
+
<h1>{{appName}}</h1>
|
|
17
|
+
<h1>Invalid link!</h1>
|
|
18
|
+
<p>No link sent. User not found or email already verified.</p>
|
|
19
|
+
</body>
|
|
20
|
+
|
|
21
|
+
</html>
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a verify email link with a
|
|
4
|
+
security token that is expired, then requests to receive another email
|
|
5
|
+
with a new link and the email is sent successfully.
|
|
6
|
+
-->
|
|
7
|
+
<html>
|
|
8
|
+
|
|
9
|
+
<head>
|
|
10
|
+
<title>Email Verification</title>
|
|
11
|
+
</head>
|
|
12
|
+
|
|
13
|
+
<body>
|
|
14
|
+
<h1>{{appName}}</h1>
|
|
15
|
+
<h1>Link sent!</h1>
|
|
16
|
+
<p>A new link has been sent. Check your email.</p>
|
|
17
|
+
</body>
|
|
18
|
+
|
|
19
|
+
</html>
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a verify email link and the
|
|
4
|
+
email gets verified successfully.
|
|
5
|
+
-->
|
|
6
|
+
<html>
|
|
7
|
+
|
|
8
|
+
<head>
|
|
9
|
+
<title>Email Verification</title>
|
|
10
|
+
</head>
|
|
11
|
+
|
|
12
|
+
<body>
|
|
13
|
+
<h1>{{appName}}</h1>
|
|
14
|
+
<h1>Email verified!</h1>
|
|
15
|
+
<p>Successfully verified your email for account: {{username}}.</p>
|
|
16
|
+
</body>
|
|
17
|
+
|
|
18
|
+
</html>
|
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when someone clicks a valid 'reset password' link.
|
|
4
|
+
Users should feel free to add to this page (i.e. branding or security widgets)
|
|
5
|
+
but should be sure not to delete any of the form inputs or the javascript from the
|
|
6
|
+
template file. This javascript is what adds the necessary values to authenticate
|
|
7
|
+
this session with Parse.
|
|
8
|
+
The query params 'username' and 'app' hold the friendly names for your current user and
|
|
9
|
+
your app. You should feel free to incorporate their values to make the page more personal.
|
|
10
|
+
If you are missing form parameters in your POST, Parse will navigate back to this page and
|
|
11
|
+
add an 'error' query parameter.
|
|
12
|
+
-->
|
|
13
|
+
<html>
|
|
14
|
+
|
|
15
|
+
<head>
|
|
16
|
+
<title>Password Reset</title>
|
|
17
|
+
</head>
|
|
18
|
+
|
|
19
|
+
<body>
|
|
20
|
+
<h1>{{appName}}</h1>
|
|
21
|
+
<h1>Reset Your Password</h1>
|
|
22
|
+
<noscript><p>We apologize, but resetting your password requires javascript</p></noscript>
|
|
23
|
+
<p>You can set a new Password for your account: {{username}}</p>
|
|
24
|
+
<br />
|
|
25
|
+
<p>{{error}}</p>
|
|
26
|
+
<form id='form' action='{{publicServerUrl}}/apps/{{appId}}/request_password_reset' method='POST'>
|
|
27
|
+
<input name='utf-8' type='hidden' value='✓' />
|
|
28
|
+
<input name="username" type="hidden" id="username" value="{{username}}" />
|
|
29
|
+
<input name="token" type="hidden" id="token" value="{{token}}" />
|
|
30
|
+
<input name="locale" type="hidden" id="locale" value="{{locale}}" />
|
|
31
|
+
|
|
32
|
+
<p>New Password</p>
|
|
33
|
+
<input name="new_password" type="password" id="password" />
|
|
34
|
+
<p>Confirm New Password</p>
|
|
35
|
+
<input name="confirm_new_password" type="password" id="password_confirm" />
|
|
36
|
+
<br />
|
|
37
|
+
<p id="password_match_info"></p>
|
|
38
|
+
<br />
|
|
39
|
+
<button id="change_password">Change Password</button>
|
|
40
|
+
</form>
|
|
41
|
+
|
|
42
|
+
<script>
|
|
43
|
+
window.onload = function() {
|
|
44
|
+
document.getElementById("password").oninput = validatePassword;
|
|
45
|
+
document.getElementById("password_confirm").oninput = validatePassword;
|
|
46
|
+
document.getElementById("change_password").disabled = true;
|
|
47
|
+
|
|
48
|
+
function validatePassword() {
|
|
49
|
+
var pass2 = document.getElementById("password").value;
|
|
50
|
+
var pass1 = document.getElementById("password_confirm").value;
|
|
51
|
+
if(pass1 !== pass2) {
|
|
52
|
+
if(document.getElementById("password_confirm").value) {
|
|
53
|
+
document.getElementById("change_password").disabled = true;
|
|
54
|
+
document.getElementById("password_match_info").innerHTML = "Must match the previous entry";
|
|
55
|
+
}
|
|
56
|
+
} else {
|
|
57
|
+
document.getElementById("change_password").disabled = false;
|
|
58
|
+
document.getElementById("password_match_info").innerHTML = "";
|
|
59
|
+
}
|
|
60
|
+
}
|
|
61
|
+
}
|
|
62
|
+
</script>
|
|
63
|
+
</body>
|
|
64
|
+
|
|
65
|
+
</html>
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a password reset link with parameters
|
|
4
|
+
that are missing or incorrect. This can either mean the user has incorrectly
|
|
5
|
+
entered a link or this could be a sign of a malicious user trying to tamper
|
|
6
|
+
with your app.
|
|
7
|
+
-->
|
|
8
|
+
<html>
|
|
9
|
+
|
|
10
|
+
<head>
|
|
11
|
+
<title>Password Reset</title>
|
|
12
|
+
</head>
|
|
13
|
+
|
|
14
|
+
<body>
|
|
15
|
+
<h1>{{appName}}</h1>
|
|
16
|
+
<h1>Invalid password reset link!</h1>
|
|
17
|
+
</body>
|
|
18
|
+
|
|
19
|
+
</html>
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
<!DOCTYPE html>
|
|
2
|
+
<!--
|
|
3
|
+
This page is displayed when a user opens a reset password link, then submits
|
|
4
|
+
the form with a new password and the password gets updated successfully.
|
|
5
|
+
-->
|
|
6
|
+
<html>
|
|
7
|
+
|
|
8
|
+
<head>
|
|
9
|
+
<title>Password Reset</title>
|
|
10
|
+
</head>
|
|
11
|
+
|
|
12
|
+
<body>
|
|
13
|
+
<h1>{{appName}}</h1>
|
|
14
|
+
<h1>Success!</h1>
|
|
15
|
+
<p>Your password has been updated.</p>
|
|
16
|
+
</body>
|
|
17
|
+
|
|
18
|
+
</html>
|