• Re: Sysop to create new user

    From g00r00@1:129/215 to Borax Man on Sat May 16 17:07:10 2020
    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.

    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).

    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.

    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.

    --- Mystic BBS v1.12 A46 2020/05/11 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From g00r00@1:129/215 to Borax Man on Sun May 17 11:55:02 2020
    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.

    Yes it does. Make sure you're using the version I pointed you to. :)

    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.

    Yes you can do that. Or use the Matrix. Or create using the user editor (if you're using the latest version).

    --- Mystic BBS v1.12 A46 2020/05/16 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)