Neeraj
c2833d11b0
[server] Panic instead of fatal err ( #5178 )
2025-02-26 14:00:17 +05:30
Neeraj Gupta
f907303c8b
[server] move files
2025-02-21 12:08:16 +05:30
Neeraj Gupta
e6e4540671
[server] Fix error type for bad request
2025-01-20 16:42:08 +05:30
Neeraj
7e320693a1
[server] Remove unused endpoint ( #4772 )
...
## Description
No logs for request in last 30 days and client code also don't refer to
this endpoint.
## Tests
2025-01-20 11:09:31 +05:30
Neeraj Gupta
5c7127cba9
Fix lint
2025-01-16 17:38:52 +05:30
Neeraj Gupta
b871f00150
Fix pkg version
2025-01-16 17:35:12 +05:30
Neeraj Gupta
bc8ebab531
clean up
2025-01-16 17:32:11 +05:30
Neeraj Gupta
5302f67679
[server] Update srp validation
2025-01-16 15:20:50 +05:30
mngshm
f34624e0d2
fix lint (?)
2025-01-06 11:39:36 +05:30
Neeraj Gupta
a1e97239c3
[server] Skip sending ott during signup when registrations are disabled ( #4563 )
...
## Description
## Tests
2025-01-01 14:39:00 +05:30
Neeraj Gupta
42a8b5c826
[server] Rename accountUrl -> accountsUrl
2024-12-24 15:25:04 +05:30
Neeraj Gupta
4cb11f4b06
[server] Return accounts & familyUrl
2024-12-21 11:56:43 +05:30
Manav Rathi
c5ffdfd091
Add internal.disable-registration to config ( #4238 )
...
## Description
As discussed in #2476 , I added an option `internal.disable-registration`
to allow disabling the registration of new users on selfhosted
instances.
Users can still go through the registration flow, but when entering the
ott they received via mail, they get an unauthorized error.
Should this be documented in any of the self-hosting documentation?
2024-11-30 05:56:43 +05:30
Neeraj Gupta
d3d419e12d
[server] RateLimit max sessions in an hour
2024-11-29 19:33:36 +05:30
Julian Pollinger
aed7075a13
invert if condition
2024-11-29 14:50:46 +01:00
Julian Pollinger
39f2d03e74
add internal.disable-registration to config
2024-11-29 00:44:33 +01:00
Neeraj Gupta
04ee6f8161
[server] Create totpSession when both passkey and totp are enabled
2024-11-27 14:54:24 +05:30
Neeraj Gupta
ccc6981df9
[server] Fix usage cal in user_details
2024-11-26 14:26:17 +05:30
Neeraj Gupta
cd1b0b1f6a
[server] Add registration check for login
2024-11-26 06:59:32 +05:30
Neeraj Gupta
338c2ec369
[server][delete] return list of apps being used
2024-11-22 16:17:08 +05:30
Neeraj Gupta
f93885fba3
[server] Return passkey acount
2024-11-22 13:01:52 +05:30
Neeraj Gupta
f37b25a1c7
[server]Throw err if account registration is completed
2024-11-21 17:26:32 +05:30
Manav Rathi
af6feaf735
[server] Remove unused roadmap related endpoints
2024-09-09 13:46:54 +05:30
Neeraj Gupta
236d24c79b
[server] Gracefully handle deleted users
2024-08-29 18:01:06 +05:30
Neeraj Gupta
f67516f696
[server] Remove duplicate code
2024-08-27 10:56:56 +05:30
Neeraj Gupta
65497862ea
[server] Remove unused endpoint
2024-08-27 10:48:56 +05:30
Neeraj Gupta
6786491d72
[server] Add admin endpoint to add ott
2024-08-24 15:35:53 +05:30
vishnukvmd
92ab8e5289
ente -> Ente
2024-08-22 18:12:08 +05:30
vishnukvmd
8b40f70936
Simply email verification template
2024-08-22 17:06:10 +05:30
Manav Rathi
53140de879
[server] Tweak verification email
...
Despite all of our efforts, gmail insists on marking our verification emails to
new users as spam. We have already changed our mail delivery providers;
non-gmail users don't face this problem; and even for gmail, (a) existing Ente
users also get these mails correctly with SPF/DKIM/DMARC PASS, and (b)
non-verification emails get delivered (in the anecdotal reports we've received).
As an attempt at some voodoo, try changing the subject and content of the mail,
to try and rule out some faulty gmail classifier that uses the email body.
2024-06-23 00:07:31 +05:30
Neeraj Gupta
186981014e
Fix typo
2024-06-12 16:40:12 +05:30
Neeraj Gupta
c95260a228
Reduce account jwt token validity to 30mins
2024-06-12 14:13:52 +05:30
vishnukvmd
39a706ea20
Update verification email address
2024-05-25 18:47:19 +05:30
Neeraj Gupta
c73dc36a8c
[Server] Fix data cleanup pipeline for recovered account ( #1410 )
...
## Description
For accounts that were recovered post deletion (within x days), we were
not removing the entry from data_cleanup cron.
The data_clean up cron anyways verify that the account is indeed deleted
before proceeding with deletion, so it was not causing any harm, but the
cron was logging error.
## Tests
- [x] Verify that data clean up entry is removed if the account is
recovered
- [x] Verify that for existing data_cleanup entry for already recovered
account, the entry is deleted from cron.
2024-04-15 10:09:29 +05:30
Neeraj Gupta
02e8861e96
[server] Remove entry from data cleanup on account recovery
2024-04-11 10:54:38 +05:30
Neeraj Gupta
339d728774
[server] Handle no user err gracefully
2024-04-11 10:29:39 +05:30
Neeraj Gupta
46188313ad
Minor refactor
2024-04-09 11:20:45 +05:30
Neeraj Gupta
73eacfb30d
[server] Use correct app while updating ott table
2024-04-09 11:14:44 +05:30
vishnukvmd
77276d8d6c
[server] Add admin API to change email address
2024-03-13 17:31:38 +05:30
Neeraj Gupta
1f7d9dbb86
Rename passKey to passkey
2024-03-08 15:15:00 +05:30
Neeraj Gupta
7f66714d96
Refactor + bug fixes
2024-03-08 15:15:00 +05:30
Neeraj Gupta
980ab6c49c
Refactor: extend totp recovery API to recover passkey
2024-03-08 15:15:00 +05:30
Neeraj Gupta
fe181fecbe
Rename
2024-03-08 15:15:00 +05:30
Neeraj Gupta
50c3a7a8e5
Store resetSecret in encrypted form
2024-03-08 15:15:00 +05:30
Neeraj Gupta
f766484b2e
Rename account_recovery -> two_factor_recovery
2024-03-08 15:15:00 +05:30
Neeraj Gupta
42e4364fda
Add APIs to allow user to skip passkey based two-fa
2024-03-08 15:15:00 +05:30
Neeraj Gupta
09a7d557d2
Add API to get account two recovery status
2024-03-08 15:15:00 +05:30
Neeraj Gupta
531bb344fe
Import museum
2024-03-01 13:37:01 +05:30
