I am looking to possible create a private BBS. One thing I want to do,
is not allow people to create an account. Rather, they would apply by other means (e-mail), and a sysop would create the account and send them the login details.
Is there a way for a sysop to create a new Mystic BBS account? Once you disable the ability to create a new user, there seems to be no other way to create a user, not with the user editor either.
Is there a way for a sysop to create a new Mystic BBS account? Once you disable the ability to create a new user, there seems to be no other way to create a user, not with the user editor either.
It shouldn't be too much effort to allow users to be created in the user editor, but the way Mystic is designed to handle this scenario is with
the Matrix login.
There are a few ways you could accomplish this but Mystic has a "matrix" login system which is designed for this exact purpose. The user is given the option to "apply" for an account but they never get into the BBS until you approve the application.
To experiment with this, go into System Configuration > Login Settings and set the following options:
Use Matrix Login: Yes
Matrix Password: <no value>
Matrix ACS: s20
In a default Mystic installation, new users are given a security level of 10. Because you set the Matrix ACS to "s20" they would never be able to login until you manually upgraded them to Security Profile 20.
What the user sees when the connect are two options: "(A)pply" or "(L)ogin". If the try to login before you approve them it will say they have not been approved yet (until you manually upgrade them to security 20).
It shouldn't be too much effort to allow users to be created in the user editor, but the way Mystic is designed to handle this scenario is with the Matrix login.
If you really didn't want users to be able to Apply online (ONLY via email) then you could do something like limit the "(A)pply" option to a local-only node, and automate the "(L)ogin" command for non-local connections. Personally doing this doesn't make sense to me since the application workflow is pretty much identical either way, but to each their own! :)
If you set it up this way then remote connections would never be given the option to Apply for a new account, instead they would immediately be given the login prompt. Only when you connected via the local console would you get a menu to Login or Create a new account.
It shouldn't be too much effort to allow users to be created in the
user editor, but the way Mystic is designed to handle this scenario
is with the Matrix login.
Just a heads up: I added the ability to create within the user editor and that will be in a build that goes up sometime today at
www.mysticbbs.com/downloads/prealpha
I've tried this, and without a Matrix password, the user is able to
select "L" and login, after creating their account intially and
returning to the Matrix Menu. With a password put in, they need to
enter a password to proceed.
This doesn't happen, despite the fact they have a security level of 10, and I set the Matrix ACS level s20.
This might be the better option. It is OK to create the accounts
locally, then simply give the user the ability to log in, passing on the details. If there is a way to allow Login for external connection, but Apply for local only, that would solve the problem.
Is there a way for a sysop to create a new Mystic BBS account? Once you disable the ability to create a new user, there seems to be no other way to create a user, not with the user editor either.
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 60 |
Nodes: | 4 (0 / 4) |
Uptime: | 23:46:19 |
Calls: | 516 |
Files: | 7,033 |
Messages: | 288,229 |