MYSQL Kalonline Setup -

[Sount]

Hello

My Name is Sount
I am new to the forums and i need a request help


a quick text tutorial how to setup a kalonline private server in mysql

I have already searched for days and found nothing. i am not experienced, and sorry if i post in wrong forums^^

 

[Sount]

Now i need a account to login , i downloaded koam. But its not working as it should be.


UPDATE :
Running als administrator solved the isue ^^

When i start the server authserver, etc i get a box with db login it asks me for id and password anyone know the id or password?

 

[rogan12]

It should be the same Id and Pw you used for MsSql.
regards
rogan12

 

[Sount]

I don't have a account i use windows authentication how i create a account?

 

[rogan12]

Easy. In the SQL manager add a user ( usually the username: sa )and give this user ownership of kal_auth and kal_db .

regards
rogan12

 

[Sount]

Could u explain in steps?
do u mean Studio Express or Server configuration manager?

 

[rogan12]

In Studio Express > expand Security and i guess you can figure it out from there

Off topic :
P.S. Microsoft Security Essentials is one of the worst antivirus tools. I would considder getting something else.

 

[Sount]

Do i need create a new login or use sa? and how i give it ownership of kal_db and auth?

I have created a new user account as shown here in this picture

 

[rogan12]

Just use the "sa" db user. Find Login and user mapping. You can configure ownerships there.
Btw. After you choose a password for sa, you have to edit the ODBC connections again with the user sa

 

[Sount]

Ok i deleted the user account i have created. ( HL )
Now after opening sa properties and going to user mapping and checking kal auth + db , after that press ok i get the following error 15405

 

[rogan12]

You forgot to mark db_owner, and only mark kal_aut and kal_db.

 

[Sount]

Still have the error , shown here in picture ( I will make new topic because these all is unrelated to mysql kalonline setup )

 

[crosenblum]

There are two methods for logging in, into sql server.

Windows Authentication, which takes the windows user account, and allows you to login with that.

Or the "sa" username and password, which should never be used in any web programming, as it gives access to all databases, to do anything.

So when koam is asking for a username/password it is asking for the sa username and password.

However, what I did, because I am a tad more sql knowledgeable was create two new kal users inside sql server, and then gave cross permissions for each database.

Then in permissions strictly limited what tables, and what access each user had.

So that some tables would be read/write only, with no delete options, etc.

In case of sql injection, by limiting what the odbc/sql user has access to, will limit possible damage.

By default the "sa" user has a blank password, which is horribly bad for security.

But it helps get you started.