Create login + license system in C#
Budget: $10 – $30 USD
5.1 Security and Access
5.1.1 Security Setup
The application must have a security module attached, the system should ship with an
Admin user, this password must be changed after first access. Passwords must be
encrypted.
5.1.2 User Access
Admin users may create new user accounts. For now, there is no need to limit the
number of users on the system. Users should be able to login and work simultaneously.
Users must be restricted as follow:
Access to various master setups must be configurable
Access to update various fields and values must be configurable
Access to certain reports must be configurable
Access to sites and locations must be configurable
Ideally user classes must be enabled, user class configuration can then be applied
to various users
5.1.3 Login Screens and Menu’s
Developers are encouraged to develop login screens and menus that promotes ease of
use while maintaining integrity of the system functionality without compromising
security or integrity.
5.2 System licensing and limitations
The product will be licensed, in other words once a year the product license renewal
will be required. Each site to be limited to ten (10) supply chain resources. Sites should
be licensed.
I company with a single license will be able to create a single site with 10 supply chain
resources.
Additional licenses can be purchased for 1 more site or 10 more warehouses.
On license expiration there may be a 30-day grace period, once a new license is loaded
depending on the expiration of the prior license the new license is valid from the date of
prior license expiration for 12 months.
After the grace period, data must continue to update, however users must be limited to
the license update screen.
The system MUST alert the users when the license is 60 days from expiration and again
30 days prior to expiration, 7 days prior to expiration, and then daily during the grace
period.
The developer must build logic for the updating of licensing and must build the solution
to generate new license keys.
5.1.1 Security Setup
The application must have a security module attached, the system should ship with an
Admin user, this password must be changed after first access. Passwords must be
encrypted.
5.1.2 User Access
Admin users may create new user accounts. For now, there is no need to limit the
number of users on the system. Users should be able to login and work simultaneously.
Users must be restricted as follow:
Access to various master setups must be configurable
Access to update various fields and values must be configurable
Access to certain reports must be configurable
Access to sites and locations must be configurable
Ideally user classes must be enabled, user class configuration can then be applied
to various users
5.1.3 Login Screens and Menu’s
Developers are encouraged to develop login screens and menus that promotes ease of
use while maintaining integrity of the system functionality without compromising
security or integrity.
5.2 System licensing and limitations
The product will be licensed, in other words once a year the product license renewal
will be required. Each site to be limited to ten (10) supply chain resources. Sites should
be licensed.
I company with a single license will be able to create a single site with 10 supply chain
resources.
Additional licenses can be purchased for 1 more site or 10 more warehouses.
On license expiration there may be a 30-day grace period, once a new license is loaded
depending on the expiration of the prior license the new license is valid from the date of
prior license expiration for 12 months.
After the grace period, data must continue to update, however users must be limited to
the license update screen.
The system MUST alert the users when the license is 60 days from expiration and again
30 days prior to expiration, 7 days prior to expiration, and then daily during the grace
period.
The developer must build logic for the updating of licensing and must build the solution
to generate new license keys.