-
Notifications
You must be signed in to change notification settings - Fork 9
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.
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
Add support for MPSK #744
Comments
To give a few pointers to anyone willing to work on this:
pycroft/web/blueprints/host/__init__.py Lines 209 to 327 in 865ebcf
Lines 110 to 221 in 865ebcf
|
added a new Subsection for MPSK Clients for the creating of them #744
added the database model for storing added the needed functions as well as the relation to the user and back Signed-off-by: Alex <[email protected]> #744
I would add a not null for the name so its better identifiable I currently also added another tab instate of putting it below the old one, first it looks way cleaner at the fronted side and in code as well as it is better structured |
changed the name Signed-off-by: Alex <[email protected]> #744
now enforces name for mpsk client refactoring changed name Signed-off-by: Alex <[email protected]> #744
First of all thank you @agmes4 :) I see that you use „WLAN“ in your implementation at the moment. |
Your totally right will change this thanks :) |
refactoring and renaming for better usability Signed-off-by: Alex <[email protected]> #744
added the api background for adding mpsk clients and editing them Signed-off-by: Alex <[email protected]> #744
added delete api endpoint for mpsks clients so they can be removed Signed-off-by: Alex <[email protected]> #744
Signed-off-by: Alex <[email protected]> #744
@agmes4 feel free to create a |
Signed-off-by: Alex <[email protected]> #744
added the naming constraint that names can not be empty or just be constructed out of witespaces Signed-off-by: Alex <[email protected]> #744
added tests for the model of mpsk Signed-off-by: Alex <[email protected]> #744
added a new Subsection for MPSK Clients for the creating of them #744
added the database model for storing added the needed functions as well as the relation to the user and back Signed-off-by: Alex <[email protected]> #744
now enforces name for mpsk client refactoring changed name Signed-off-by: Alex <[email protected]> #744
added the database model for storing added the needed functions as well as the relation to the user and back Signed-off-by: Alex <[email protected]> #744
now enforces name for mpsk client refactoring changed name Signed-off-by: Alex <[email protected]> #744
refactoring and renaming for better usability Signed-off-by: Alex <[email protected]> #744
added the naming constraint that names can not be empty or just be constructed out of witespaces Signed-off-by: Alex <[email protected]> #744
added tests for the model of mpsk Signed-off-by: Alex <[email protected]> #744
there was a small error which just checked rather Signed-off-by: Alex <[email protected]> #744
removed the old decorator Signed-off-by: Alex <[email protected]> #744
Signed-off-by: Alex <[email protected]> #744
added the user who deleted the mpsk client as processor Signed-off-by: Alex <[email protected]> #744
added an error indecating the maximum amount of clients was exceeded added a check for the client to exceed the maximum number of mpsks devices Signed-off-by: Alex <[email protected]> #744
checking for amount exceeded error as well as naming error in MPSKS clients Signed-off-by: Alex <[email protected]> #744
added a test for too much mpsks clients added Signed-off-by: Alex <[email protected]> #744
added key arg which is for determining rather the amount of mpsks clients should be validated for a amount Signed-off-by: Alex <[email protected]> #744
added test for clients exceeding admin fixed test for api call Signed-off-by: Alex <[email protected]> #744
changed the creat mpsks so that it now validates for the length of added clients Signed-off-by: Alex <[email protected]> #744
the api is now able to add more clients Signed-off-by: Alex <[email protected]> #744
Signed-off-by: Alex <[email protected]> #744
added the db session now as parameter removed kargs for determining api calls moved check for number of mpsks clients to api Signed-off-by: Alex <[email protected]> #744
added same mac test, invalid password, exceeds the max clients added delete mpsk; test not found, unauthed, successful delete Signed-off-by: Alex <[email protected]> #744
refactored code renamed some error codes for better readability Signed-off-by: Alex <[email protected]> #744
added get mpsks clients tests Signed-off-by: Alex <[email protected]> #744
added api route for getting all the mpsks clients of a user Signed-off-by: Alex <[email protected]> #744
added test for changing the mpsk clients Signed-off-by: Alex <[email protected]> #744
changed the error codes for changing mpsk client so they match the ones in adding Signed-off-by: Alex <[email protected]> #744
Signed-off-by: Alex <[email protected]> #744
added karg parameter Signed-off-by: Alex <[email protected]> #744
fixed the typo for show user from tasks to mpsk_clients Signed-off-by: Alex <[email protected]> #744
In order for MPSK to be used by our members, an appropriate frontend, including an API endpoint, must be implemented.
The following SQL schema is currently planned:
A MAC address must be uniquely assignable to a user. However, a user can create as many MAC addresses as they wish.
To better distinguish between devices, it is planned to allow users to assign names to their devices.
The frontend can thus be implemented similarly to the existing interface list. This can then be placed in a separate tab, "WiFi" or similar, on the user page.
To simplify troubleshooting in case of issues, a note should be added in the frontend if the user has a legacy WiFi password that is not stored in plain text. (Reminder: WiFi password ≠ login password)
Feel free to ask questions if necessary.
The text was updated successfully, but these errors were encountered: