EVE Technology Lab

In debugging my issues with broadcasting I've gone into the shell and stepped through the code from allianceauth/services/managers/openfire_manager.py. I first import everything and then issue the commands from the send_broadcast_message method. Here's the complete output, but one area catches my attention:

After issuing the command
It's returning an error

This occurs for the broadcast username/password combination in settings.py as well as when I substitute in my personal username/password which I can connect with using Pidgin.

Anyone have an idea what I should be looking into? As far as I can see the shell opens a connection to the jabber server but is getting hung up when it tries to authenticate.


It seems I can only fix things when I post about it on the forums.
Solution: when setting up OpenFire, when you name the server, call it

Quote:

yourdomain.com

otherwise the auth system will have issues loggin in as broadcast user. If you've already configured it just change the xmpp.domain setting to your domain and restart.

Taking a cursory glance at the code, all I can see are API calls checking current corps of characters on the key. Key type is only enforced when adding the key here.

I've never tried bypassing that, but commenting out those checks and then testing with a non-account non-full API key would tell you in a hurry what's broken. Just note that disabling key type enforcement means people can register with "blank" keys (enough to pull a character+corp iirc) which means auditing them in the Corporation Stats page would be rather pointless.

Edit: eve_api_manager.py, line 18 might throw an exception. Not sure if character-restricted APIs have an "account" to reference.

Thanks for the info! Do you think it would be possible to change it from a full API to a specific access mask? Or would this involve adding complicated code or some such?

Sorry about the unannounced leave. Life gets in the way at times. So few things to note.

1. Thanks everyone who is supporting others when trying to setup the auth.
2. Thanks to those who have submitted patches and bug fixes.


However i would like to state that development of the auth is now frozen. This is not to say that i will not be checking pull request and incorporating them into the main development branch. Simply put i am not happy with how it turned out. There are a few things i did wrong because i was in a hurry that make the auth system rather difficult to extend without fully understanding the core design. Specifically adding new services is a nightmare.

So i can't say when but a rewrite will happen when i have more free time to pursue this. Here is a list of the current issues with the auth.

1. Not enough error handling
- There are still some errors that occur and just return 500's

2. Services are not abstracted interfaces.
- Reason adding new services takes so long.

3. No use of any sorta rest api/jquery.
- The current interface is anything but modern where there should be rest api calls and ajax there is just page reloading.

4. No available api built in for third party applications.
- Because of the way its written adding in a api for third party applications is a disaster waiting to happen.

5. Reliant on the soon to be depreciated api
- Needs to make use of the crest api, although im not to sure on the depreciating of the current api.

6. Its to damn difficult for the average joe to setup.
- At first i thought it wouldn't be an issue but the more and more emails i and others get proves that it is still far to difficult to setup.

There is my rant and my current issues with the code thats been written. Like i said before this does not mean i won't be updating the github with the latest pull request and bug fixes it just means i personally will not be developing this system anymore.

Until you realize that the jabber protocol and mumble don't support spaces and breaks entirely ;)

willing to pay for installation on my server for a small alliance with a couple of friendly corps

please eve-mail me on Nomak or even better skype me on dwf.nomak
thanks

Just realized IP Board supported version is 3.x. Unfortunately, I did install version 4.

Any project to update to next ip board version ?
Some more documentation about IP Board and Teamspeak possible ?

One last question is :

- I'm looking to SSO (Single Sign On) some projects availble on the techlabs forums or elsewhere, like LMEve, IPB Wiki, ECM, ... and prevent users to have to register 4 times, or more. What you could give me as advice to accomplish this using the best way ?

Important about that is to define one registration location & managing roles.

Thanks.

Ok, hate to be the guy what is stuck near the beginning, but have tried doing these processes a couple of times, including from scratch, and I'm sure I'm missing something simple.

I got this error when trying to start Alliance Auth with python manage.py syncdb

Image of code

Followed everything else to a T (I think) but not sure where I'm going wrong.

Any advice?

I've tried the sudo in front, here's the screenshot

Is it possible to use this for a corporation not in an alliance?