30 Commits

Author	SHA1	Message	Date
Harvey Tindall	213b1e7f9e	accounts: allow setting exact expiry date ... set with a text input field which uses the same date parsing library as the search function. Parsed expiry date will appear once you've typed something in, so you can make sure it's right.	2023-12-20 17:20:59 +00:00
Harvey Tindall	10c8d4ad2f	accounts: add "remove expiry"	2023-11-16 11:19:49 +00:00
Harvey Tindall	a66c522b73	referrals: add "use expiry" option ... adds an option when enabling referrals to use the duration of the source invited (i.e., months, days, hours) for the referral invite. If enabled, the user won't be able to make a new referral link after it expires. For referrals enabled for new users via a profile, the clock starts ticking as soon as the account is created.	2023-11-10 15:07:29 +00:00
Harvey Tindall	44172074b9	activity: render all activities correctly ... the activity type, usernames, time, referrer, and invite code are displayed correctly for all types of activity.	2023-10-21 13:00:06 +01:00
Harvey Tindall	9d1c7bba6f	activity: log account link/unlinks	2023-10-19 21:17:03 +01:00
Harvey Tindall	b620c0d9ae	activity: implement most initial logging ... resetPassword, changePassword, delete/createInvite, enable/disable, creation/deletion of invites & users are all done, only remaining one is account linking.	2023-10-19 18:56:35 +01:00
Harvey Tindall	2c787b4d46	activity: log creations	2023-10-19 18:14:40 +01:00
Harvey Tindall	77f6b1042e	invites: move code gen to function ... code to generate an invite code w/ a non-integer first character was reused a bunch, so it's now function GenerateInviteCode().	2023-10-11 11:30:28 +01:00
Harvey Tindall	cf94fdb2f0	ombi: fix password reset on default route ... the ombi password wasn't being changed w/ password resets initiated through the admin page (and probably by other routes, too), as the code was considering a HTTP 204 from Jellyfin as a failure, causing it to skip anything with Ombi. Also added a little check for Ombi-imported accounts that probably won't help with anything, but whatever.	2023-10-09 10:40:40 +01:00
Harvey Tindall	dae0ad1de5	invites: "User Label" 2/2 ... applies label to users. Also hide the user label element on the invite dropdown when not set.	2023-09-08 14:37:07 +01:00
Harvey Tindall	0b830e9b5e	referrals: enable for new users from profile	2023-09-07 14:31:42 +01:00
Harvey Tindall	db21131185	accounts: allow disabling of referrals for users	2023-09-07 14:00:30 +01:00
Harvey Tindall	729552a827	referrals: Show enabled status on account list	2023-09-06 22:46:16 +01:00
Harvey Tindall	9e5034ebab	referrals: enable referral for users & profiles ... Enabling for individual users works, as does adding a template to a profile. Removing/Disabling for both needs to be completed.	2023-09-06 22:00:44 +01:00
Harvey Tindall	9c2f27bcdb	referrals: 1/2 generation routes, display route, partial frontend ... route for generation/enabling of referral for user(s) done? the frontend is mostly done, but functionality is not there yet. Route for finding and displaying referral to user is done. Also the config option for referral is there, in user page settings.	2023-06-28 16:05:24 +01:00
Harvey Tindall	b17d8424e9	profiles: fix application ... moving to a DB meant empty slices in the Configuration & Policy structs were being stored as null, and striking a nerve with Jellyfin. Mediabrowser library change fixed that by de-nulling them itself, and a new bool field called "Homescreen" is now used to decide if a profile has a homescreen layout stored or not. This field is hopefully correctly filled in during migration.	2023-06-26 13:01:17 +01:00
Harvey Tindall	9c84fb5887	profiles: fully deprecate old system ... ombi_template, configuration, displayprefs, and policy still stuck around for the admin new user feature. They are now sourced from the default profile, and eventually a feature to select the source (or no source) will be added. this was still used when creating a new user as admin for some reason. template is now sourced from the default profile.	2023-06-25 18:59:55 +01:00
Harvey Tindall	a735e4ff29	db: migrate user profiles	2023-06-24 21:29:54 +01:00
Harvey Tindall	63948a6de0	db: migrate invites, user expiry ... some fixes to stuff in there too, probably	2023-06-24 19:13:05 +01:00
Harvey Tindall	833be688ac	storage: start db migration (badger(hold)) ... migrating to badger, with the badgerhold frontend. So far, done: * Announcements (small, for a quick test) * Discord/Telegram/Matrix/Email most interaction with badgerhold is done through the standard Get<x>/Get<x>Key/Set<x>Key/Delete<x>Key. UserExists functions have been added for email and matrix, and those and the original ones now use a query against the database rather than sifting through every record. I've tagged these searched fields as "index" for badgerhold, although this definitely isn't used yet, and i'm not entirely sure if it'll be useful. migrateToBadger is now in migrations.go, and a temporary config key "migrated_to_badger" has been added, although it isn't being used yet, migration is just running every time during development.	2023-06-24 17:05:04 +01:00
Harvey Tindall	97db4d714a	userpage: implement change password functionality	2023-06-22 20:54:52 +01:00
Harvey Tindall	14c18bd668	form: rework email confirmation ... realized half the info from the signup form wasnt being stored in the JWT used to create the account after email confirmation, and instead of adding them, the -whole request- from the browser is stored temporarily by the server, indexed by a smaller JWT that only includes the invite code. Someone complained on reddit about me storing the password in the JWT a while back, and although security-wise that isn't an issue (only the server can decrypt the token), it doesn't happen anymore. Happy?	2023-06-21 21:14:41 +01:00
Harvey Tindall	f779f0345e	storage: Use familiar api for invite access ... An almost identical set of functions to the discord/telegram/matrix storage ones is now used for accessing invites. No more parallelism-related issues, yay. Need to do this for everything eventually.	2023-06-21 20:39:16 +01:00
Harvey Tindall	ebacfd43be	form: fix captcha, matrix, telegram ... new issue though: discord/telegram/matrix aren't linked when email confirmation is used!	2023-06-21 20:00:48 +01:00
Harvey Tindall	3747eaa3a7	messages: refactor dc/tg, fix tg ... less external access to Discord/TelegramDaemon internals, will be easier to keep user/admin-side uses functioning similarly. Also changed their internal token stores to use a map, and store an expiry. verifiedTokens is also now a map in telegram. Also fixed issue where token wasn't being deleted after use on the user page.	2023-06-21 18:02:33 +01:00
Harvey Tindall	68004e1d34	storage: user set/get methods for contact method access ... Get/GetKey/SetKey/DeleteKey methods are used for access to email/discord/telegram/matrix, everywhere. Mutex added for each, avoids concurrent read/write issues. Will also make potential transition to database easier.	2023-06-20 12:19:24 +01:00
Harvey Tindall	48403ce940	discord: proper support for discriminator-less ... names with no discriminator are shown as @username, and search works with the @ too. Also bumped go version to 1.20, since it was stuck on 1.16 and i felt like trying generics (in an ugly way).	2023-06-12 16:32:40 +01:00
Harvey Tindall	5d289ce023	Admin: auto enable contact when an email is added ... "Contact through email" is now automatically enabled when adding an email address to an account without one on the admin page. Solves #233.	2023-02-01 15:25:47 +00:00
Harvey Tindall	2722e8482d	Invites: unique email/ID requirement ... "Require unique ..." Settings (`require_unique` in relevant sections of config.ini) are now available for email/discord/telegram/matrix. An error is shown on the invite form if a non-unique address/ID is used. This was on my kanban without a link to an issue, so i'm guessing it was requested on Discord.	2023-02-01 15:11:10 +00:00
Harvey Tindall	12db53d1eb	reorganise api, add "Connection refused" error in setup ... fixes #201	2022-03-22 14:58:39 +00:00