[WIP] new module: SERM (Supportsuite Enhanced Right Management)

[Sheep]

(WIP = Work In Progress)

Hello everyone,

as some of you have seen, i've been writing a guide on how to make a module. That's because i'm working on a module
As i got the permissions to share it, i'll post there the progress



The purpose of the module is to get a better way to handle right on ressources (downloads, kb, troubleshooters). Currently the only way to restrict access to some ressources is to use the templates, but it's hardly usable and has major security leaks (because that's not what it's supposed to do).

What my company needs is a way to allow to some client (and deny to the others) access to specific folders depending on their rights (support level)


The best way for you to understand will be via concept arts (those are just image, there's currently nothing in fact)
Also ...I'm sorry but the descriptions are a mix of english and french (but don't worry i'll explain)

The new tab handles rights:
Manage Groups: it's a page where you create new group of rights.
There's the concept of sub-group where the group inherits of the rights of the parent.

On the following screenshot you can see my workflow with 2 of EONA's products (DES and MRS)
DES group is the first level of rights, where there are advanced informations and stuffs
AdC (Non disclosure agreement) is the second level of rights (with more advanced ressources)
MoU (Memorendum of understanding) is the final level and the higher one

That's specific to my company, but as you can see it's completly customisable.

The global and registered groups can't be removed because that's the permissions for registered and not registered users.



Now lets edit the rights of DES > AdC (NdA)

Here are my downloads categories (the rights will be only on categories, not on files).
In this group of rights we allow access to Guides and Informations (blue marks). The green mark indicates that the right is inherited through the parent. The green mark can be changed to blue to overide rights (exemple: if you remove rights in the parent group).

The presentation will certainly change.




Now lets go to the manage users
In fact it's "manage usergroups" (i'm lazzy to redraw the screenshots)

My usergroups are my clients companies (and there are serveral users in everygroups).


Lets edit IEC rights.

In this part we attach the usergroup to right of groups.
When we click on AdC the parent groups are automatically checked.
Every users in this group will get access to the ressources that we allowed for everygroup marked.


But... there should be some special exception by usergroups
As you can see, the green marks indicates the rights inherited by the groups of rights.
In blue you can check exceptions.

The main idea is to create a folder by company and then only them will access to this folder (that's doesn't require to have a group of rights).

This page is also a way to see what ressource the groups have access.


That's it. If you have questions i'll be glad to answer them.


I'm still deeply looking at kayako's code so atm there's still nothing done

If my english is not understandable in some parts, slap me here, i'll change my sentences

[Jamie Edwards]

Antoine,

I imagine a lot of us here will be very excited to follow your progress - great work!

[Chris Boulton]

Sounds like something which I could make very good use of.

Looking forward to seeing it progress.

[craigbrass]

Lookin good!

[Sheep]

Update:
Here comes the database diagram.
That should fit nicely. I don't want to get too much tables that's why i'm using one like a datawarehouse.

The link with supporsuite comes with the table swusergroup (kayako's table)
A reccord in the right table = Allow this ressource to this target


(Yes i'm using MSaccess to design... so what? :P)
and don't mind about the text type, it should be int... but well that's the design that i wanted to show you.
I'll change the "id" keys to "grouprightid", "rightid" and so on


Questions, Suggestions & Comments are welcome

[Siora]

you are doing a great job so far and proving to be a very useful asset to this forum and community. Keep up the good work.

[Sheep]

Hi everyone,
i'm looking for a trustworthy beta tester (one or more). If you have a test server (dont put this on a live server atm!) please tell me
(of course, you need to have an owned licence).

Beta1 stage has been reached and the Staff part seems to be complete and working. But i need someone to try the installation process etc... (i can't do it myself has my test server is the one where i'm programming on).

Beta2 will include the client side right checks. It might come this afternoon or monday.

thanks,
Antoine


Edit: ah, forgot to tell you that i'll be leaving the kayako's community in 2 weeks as my training course (i'm a student), in the company where i set up a support platform, is reaching it's end. Too bad :-/

[Siora]

Thats truly too bad Antoine...you've been a valuable member here for sure.

[craigbrass]

Yes Antoine, I will also be sorry to see you go. You have been a great help especially code wise to many people here.

[gmg]

Antoine,

I will be sorry to see you go as well.

I could possibly be a beta tester for you, but this is not something we currently need. We would likely need it when our SupportSuite is better linked to our Subscription System.

I just wish that someone would come up with some way to force users to login before allowing a submit of a ticket.

Mark Dahl

[Siora]

Originally Posted by gmg

Antoine,

I will be sorry to see you go as well.

I could possibly be a beta tester for you, but this is not something we currently need. We would likely need it when our SupportSuite is better linked to our Subscription System.

I just wish that someone would come up with some way to force users to login before allowing a submit of a ticket.

Mark Dahl

What do you mean? Why don't you remove the submit ticket module from the guest user group? Thats what I did and now you can't submit a ticket or see my KB without registering with us first.

[craigbrass]

Just set "Can View Submit Ticket Widget" for Guests inside Staff CP -> Users -> Manage Groups to "No".

[Sheep]

Hello guys,

i'm having a hard time reverse engineering some parts that's why i'm 3 days late (also got some other things to do) :P
beta1 is finished and beta2 going well... maybe in ... 2 days for RC1?
a video demo might come tomorow.

gmg > i'm going to use virtual servers, that's going to be easier. thanks anyway

[craigbrass]

Reverse engineering? You mean the encoded stuff?

[Sheep]

Nop
I meant, understanding the code to find the functions calls that need to be fixed.

Reverse engineering (RE) is the process of discovering the technological principles of a device or object or system through an abductive analysis of its structure, function and operation

Wikipedia

Edit: ETA: module is finished this afternoon.
Deeper tests tomorow, and release (RC1) tomorow afternoon