User Authentication

[fameal]

People, in a couple of hours I've manage to make a little and buggy login system for customers. I've made it using 2 tables: ost_clients and ost_users. The first one if for the company from which the user is, and the second for the employees which are the ones allowed to log in. As an attachment you will find the SQL sentences to create the tables. It is static, so please modify it to adjust to your schema.

The other attached files are the ones I modified to make it work. You have to replace some to make it work.

I tried to make it tidy, perhaps it's not very well right now but consider it PRE-ALPHA. It only logs the client in and redirect him/her to the client's index page.

I will continue developing to make it fully functional. Someone wants to join?

I hope it can be a kick off for every of us to start developing for to make this a better project (I think it is very very good now).

Please let me know if you have any issue.

PS: I couldn't manage to upload the files separately. I'm putting them all into a zip file. They contain the OST directory structure.

[mainstreetexile]

This looks like a pretty cool start for something that a lot of people are interested in (me and my company included). I've been looking at going another route:

1) I turned off the open Add Ticket and had everything redirect to the staff control panel login.

2) I've done some quick hacks to use the Departments functionality of osTicket (we dont have a need for this) to simulate a company/user group level of security and set up some users as Staff. This allows them to log in and only see tickets posted by other members of their department / company (I dont remember if i had to tweak this or not)

3) I've modded the new ticket form to remove the appropriate fields and replace them with hidden fields and flat text so they cant be changed easily (email address, full name, department).

They're all quick hacks and not great (the hidden fields could be modified by post, but theyre behind the login and our users probably arent that savvy) but they look like, with some more tweaking, they might work for our purposes until something else comes along (e.g. a more robust version of what you've started here).

Just thought I'd throw that out there if anyone else was interested. I'm super interested in this functionality and I'd like to help move it along.

[ttvtechie]

OK
I wanted to get a front end that required a user to login before they can do anything. I want the user to be registered with us before they can raise a ticket, and only us can register / activate a user.
I thought if I could hack this MOD I might get what I was after but because of my lack of experience it hasn't quite worked. Now when go to the ticket URL I get the message
"Fatal error..get tech support"
What have I done?
Could someone help?

I have created the tables ost_clients and ost_users by using the SQL code supplied, I have inserted 2 clients and 2 users
I have extracted the files from the zip to the osticket directory and all the files look like they are there
I edited the index.php
so
require('client.inc.php');
require(CLIENTINC_DIR.'header.inc.php');
is now

require("client.inc.php");
require("$client_dir/header.inc.php");
also the require(CLIENTINC_DIR.'header.inc.php'); at the end of the file has been replaced with require("$client_dir/header.inc.php");
I guess the error is obvious but I don't have enough experience to see the fault.
Malc

[fameal]

This looks like a pretty cool start for something that a lot of people are interested in (me and my company included). I've been looking at going another route:

1) I turned off the open Add Ticket and had everything redirect to the staff control panel login.

2) I've done some quick hacks to use the Departments functionality of osTicket (we dont have a need for this) to simulate a company/user group level of security and set up some users as Staff. This allows them to log in and only see tickets posted by other members of their department / company (I dont remember if i had to tweak this or not)

3) I've modded the new ticket form to remove the appropriate fields and replace them with hidden fields and flat text so they cant be changed easily (email address, full name, department).

They're all quick hacks and not great (the hidden fields could be modified by post, but theyre behind the login and our users probably arent that savvy) but they look like, with some more tweaking, they might work for our purposes until something else comes along (e.g. a more robust version of what you've started here).

Just thought I'd throw that out there if anyone else was interested. I'm super interested in this functionality and I'd like to help move it along.
mainstreetexile,
It seems you have it working by now. I stop developing and start thinking what's the best way to do it. Now, I have the idea that I would be nice is OST has its own tables and parameters to integrate those with another system. I think that cuold be very useful. I haven't got any more time to continue with this, but I think next week I will get some other functionality.

Please keep in contact and I know we can make something interensting. Also, I wanted to know if there are some rules to write code for it to be included into OST later. Do you know anything about that?


Best,

[fameal]

OK
I wanted to get a front end that required a user to login before they can do anything. I want the user to be registered with us before they can raise a ticket, and only us can register / activate a user.
I thought if I could hack this MOD I might get what I was after but because of my lack of experience it hasn't quite worked. Now when go to the ticket URL I get the message
"Fatal error..get tech support"
What have I done?
Could someone help?

I have created the tables ost_clients and ost_users by using the SQL code supplied, I have inserted 2 clients and 2 users
I have extracted the files from the zip to the osticket directory and all the files look like they are there
I edited the index.php
so
require('client.inc.php');
require(CLIENTINC_DIR.'header.inc.php');
is now

require("client.inc.php");
require("$client_dir/header.inc.php");
also the require(CLIENTINC_DIR.'header.inc.php'); at the end of the file has been replaced with require("$client_dir/header.inc.php");
I guess the error is obvious but I don't have enough experience to see the fault.
Malc
Malc,
I don't understand what's the issue. You copied everything into yout OSTicket instalation and it doesn't work? Why have you made those changes?


Best,

[Lionfire]

I have uploaded the cost per your instructions, but can still not get this to work whatsoever... it won't let me login... any suggestions?

[sayedyousif]

femael,
I follow the procedure you mentioned, and the login page occur to me, but what will be the username and password for client in order to log in and add request.
________
how to make a vaporizer (http://howtomakeavaporizer.info)

[sayedyousif]

when I connect to the client login form, I receive the following message:
Access Denied
________
mflb vaporizer (http://mflbvaporizer.com)

[mrgsystems]

I take this addon got forgotten about?

[saavedrams]

This looks like a pretty cool start for something that a lot of people are interested in (me and my company included). I've been looking at going another route:

1) I turned off the open Add Ticket and had everything redirect to the staff control panel login.

2) I've done some quick hacks to use the Departments functionality of osTicket (we dont have a need for this) to simulate a company/user group level of security and set up some users as Staff. This allows them to log in and only see tickets posted by other members of their department / company (I dont remember if i had to tweak this or not)

3) I've modded the new ticket form to remove the appropriate fields and replace them with hidden fields and flat text so they cant be changed easily (email address, full name, department).

They're all quick hacks and not great (the hidden fields could be modified by post, but theyre behind the login and our users probably arent that savvy) but they look like, with some more tweaking, they might work for our purposes until something else comes along (e.g. a more robust version of what you've started here).

Just thought I'd throw that out there if anyone else was interested. I'm super interested in this functionality and I'd like to help move it along.

Hi, I have been reading your solution, can you help me ? because I don't know if you can share with me your modifications on step number 3, this would be helpful for me.:D

[ozkr]

is this for 1.6 ST version?

[ozkr]

im trying to implement this but i cant log in to the client zone. How can i login? i´ve created a user in ost_users but i notice that there´s no username field. how do you log in to the client area? i think there is some thing you´re missing. plz check your files and DB.

[dkxurple]

this code seems like it should work trying to get it to query to the database correctly. has anyone gotten it to work?

[odinspark]

any hope in getting this file?