EVE Technology Lab

No problem, learnt quite a lot from him and a few others actually, so give them plugs here and there. fly safe

Running into an issue with openfire. There's some group caching going on in the background, meaning members who register after a channel has been created will not be able to join the channel until the server restarts, or the group ACL is refreshed by removing and then re-adding the group to the channel permissions.

Relevant issue: https://igniterealtime.org/issues/browse/OF-921

So far the fix has been included in Openfire 3.11.0 Alpha (Oct 24), no word on when it'll get pushed to the stable branch.

Unfortunately, it seems this build breaks the user service plugin as it's long since depreciated. So..... Nightly reboot of the jabber server is my best solution. Cronjob should do the trick. I'm looking into implementing the REST API to replace User Service plugin.

EDIT: Instead of sleeping, I went and did it. Here's a modified OpenfireManager using the REST API. Simply replace services/managers/openfire_manager.py with the above file, and then install the REST API plugin on openfire using secret key authentication with the secret key set in settings.py.

The alpha release of openfire has issues with password validation so it's a no-go.

I've been looking into this without any luck so far, mostly because I'm cheap and won't pay for IPB. Hard to test without it. However I just came across a "publicly accessible" version tonight so work can begin!

From initial inspection, "oh boy this is gonna get messy". Can't find any references to the API.

Can I convince you to use IPBoard 3?

Probably, never tried it though.

So apparently auth is not adding groups to the ip.board forums. Still working on this, but not sure if anyone had similar issues and had any suggestions.

Heyo, just an FYI for folks still watching this thread.
I completed my upgrades to the TS3 manager, making group assignment way easier.
You can now build relationships between TS3 groups and Auth groups, so rather than auth pushing those terrible group names to TS, it just compares assignments, allowing your TS admins to maintain the permissions system and bans while an Auth admin manages the group assignments.
There's still more that can be improved, but this has eliminated the funky permissions issues some folks were having.
In the future, I'm going to make a page where these group association can be managed by people with the appropriate permissions. In the meantime, there were some security improvements I wanted to make.
I think Adarnof is getting close on that Corp/Alliance toggle.

One last note, I'm working on getting in contact with R4stl1n to get contributor status on the repo for Adarnof and myself. That way we can save people the trouble of switching repos.

My fork is over at https://github.com/Kaezon/allianceauth for the time being.

It turned out that I did something bad and used 'alliance_forum' for my IPB db (the same one auth creates).

I reinstalled using a fresh db, and it creates and assigns groups fine.

Unofficially. I've been working on that for a while now and it's just about done.

My repo has two branches that can act as corp boards, "corp" and "toggle". Corp is as its name suggests, stripped down to operate on the corp level. I stopped work on it in favour of toggle, but it has fewer bugs at the moment. Togge is under active development to facilitate either alliance or corp deployments, and transition between the two.

To deploy either of these, follow the normal install instructions but when you get to the "git clone" command, put the URL for my repo instead of the original author's (https://github.com/Adarnof/allianceauth.git).

Immediately after, "cd allianceauth" and then "git checkout corp" or "git checkout toggle" for whichever branch you desire.

Feel free to get in touch if you run into any problems.

Once again - let me say:

I am a doctor by 'trade' and have pretty much zero programming experience. I have some, but very little, prior linux exposure and have worked with django on the user end via other auths...

I set this up in about a weeks time in my free time with very minimal obstacles. All of my questions were answerable via google, this thread, and the set up guide.

I tried two other open source auths - and met insurmountable obstacles that even my IT friends couldn't get me past. In fact, the biggest delays in me getting something going were because I stopped trying this auth and attempted the others.

I am truly AMAZED at what this provides us who lack extensive IT/programming experience. I kind of think Reynaldo underestimated what he created.

In fact, I spoke at fanfest last year, and hope to do so next year and am hoping to do so again. But I definitely think there is room for a 'third party IT for the complete noob" presentation. If CCP Foxfour is still following this thread - it should definitely be a thing and I have to wonder if adarnof or reynaldo plan attend?

Anyway, sorry for flooding the thread with effusive praise, but yeah - totally deserved.

I'll telll you what, I met Adarnof a month or so ago when he contacted me in game and offered to help me set it up, due to extra technical issues it took a lot longer than it should have. While I would love to send him extra isk, I am now broke as hell to much alliance leadership stuff :P So instead ive given him some plugs especially on our front page. He also introduced me to another guy who is working on the auth system in question Kaezon. These guys have been great and we talk often.


Kazeon has some great projects in the pipeline to do with it, I wont shear it as I don't want to steel his thunder but he has just made an awesome plug in with team speak auth to make it a lot better! These two guys are doing an awsome job though so just thought I would bump this thread with there names :)