CounterSoft User Forums

Welcome to CounterSoft User Forums Sign in | Join | Help
Home Forums

windows authentication fails after migrating from 2.1 to 3.6

Last post 01-15-2010, 11:47 AM by MarkWing. 5 replies.
Sort Posts:
  •  01-14-2010, 5:17 PM

    windows authentication fails after migrating from 2.1 to 3.6

    Hello,

    I'm migrating from 2.1 to 3.6 with the following scripts :
    - Upgrade_v2-2.sql
    - Create_Tables.sql
    - Create_Views.sql
    - Create_Procs.sql
    - Upgrade_v3.0-step1.sql

    The problem is that the users can't connect any more using Windows Authentication.

    I don't have an account on it and admin account was deleted. Is there a way to manually add an account in the database so I can connect ?

    Thx

  •  01-14-2010, 6:25 PM

    Re: windows authentication fails after migrating from 2.1 to 3.6

    See the create_tables script, it creates an admin account but you will need to add it to the admin group.

    What is the issue with windows auth? Do you get an error?


  •  01-15-2010, 8:39 AM

    Re: windows authentication fails after migrating from 2.1 to 3.6

    How can I add the admin in the admin group without having any access? what tables are implied?

    Well, users can't connect using windows auth because i didn't do anything yet with the groups definition. I guess i will be able to do it when i log as an admin.

    Thanks

  •  01-15-2010, 9:54 AM

    Re: windows authentication fails after migrating from 2.1 to 3.6

    Ok, if you were in forms authentication mode and just changed to windows, simply change back to forms, add your user (DOMAIN\User) and make it an admin. Switch to winodws and that should be it for you.

    To add an admin user you need:
    • Create the user (make sure the username is not in the table already, password is admin):
      • INSERT INTO gemini_users (username,firstname,surname,pwd,emailaddress,roles)
            VALUES (N'admin',N'Jon',N'Smith',0x21232F297A57A5A743894A0E4A801FC3,N'jon@smith.com',N'G!')
    • Add the user to the admin,everyone and everyone authneticated groups:
      • INSERT INTO gemini_globalgroupmembership (globalgroupid,userid)
            SELECT 1 AS globalgroupid, THE NEW USER ID
        INSERT INTO gemini_globalgroupmembership (globalgroupid,userid)
            SELECT 2 AS globalgroupid, , THE NEW USER ID
        INSERT INTO gemini_globalgroupmembership (globalgroupid,userid)
            SELECT 3 AS globalgroupid, , THE NEW USER ID


  •  01-15-2010, 10:45 AM

    Re: windows authentication fails after migrating from 2.1 to 3.6

    It's working fine Thanks!

    Windows Auth is working properly too.

    The admin account is well created in Create_Tables.sql but for some reason i don't know, it's not in the gemini_users table once every scripts are run.

  •  01-15-2010, 11:47 AM

    Re: windows authentication fails after migrating from 2.1 to 3.6

    Yes, this is because the upgrade scripts remove all entries from the new table to bring in the existing (old) data.

View as RSS news feed in XML