Beta 7 permissions still not working

Hi jadestorm,

I just installed 3.2.0 and the new beta 7. Tried the permissions but there is still a problem, actually 2 problems.

  1. permissions not working

  2. the full JID is NOT saved, only the plain username

here a snipped of my warn log


2007.02.07 22:16:51 Missing type info for savePermissions(2 in dwr.xml


turbo

is nothing in your gatewayRestrictions table?

  1. the full JID is NOT saved, only the plain username

That is correct behavior. The plugin will never save the full JID. It has no reason to since it only supports users on the local server.

here a snipped of my warn log


2007.02.07 22:16:51 Missing type info for savePermissions(2<0>). Assuming this is a map with String keys. Please add to in dwr.xml

2007.02.07 22:16:51 Missing type info for savePermissions(3<0>). Assuming this is a map with String keys. Please add to in dwr.xml

2007.02.07 22:17:24 Missing type info for savePermissions(2<0>). Assuming this is a map with String keys. Please add to in dwr.xml

2007.02.07 22:17:24 Missing type info for savePermissions(3<0>). Assuming this is a map with String keys. Please add to in dwr.xml

2007.02.07 22:17:27 Missing type info for savePermissions(2<0>). Assuming this is a map with String keys. Please add to in dwr.xml

2007.02.07 22:17:27 Missing type info for savePermissions(3<0>). Assuming this is a map with String keys. Please add to in dwr.xml

2007.02.07 22:17:30 Missing type info for savePermissions(2<0>). Assuming this is a map with String keys. Please add to in dwr.xml

2007.02.07 22:17:30 Missing type info for savePermissions(3<0>). Assuming this is a map with String keys. Please add to in dwr.xml

2007.02.07 22:17:32 Missing type info for savePermissions(2<0>). Assuming this is a map with String keys. Please add to in dwr.xml

2007.02.07 22:17:32 Missing type info for savePermissions(3<0>). Assuming this is a map with String keys. Please add to in dwr.xml

That I have yet to figure out how to silence. What it’‘s saying is fine, but I’'m trying to figure out how to shut it up.

turbo wrote:

turbo

Hi jadestorm,

I just installed 3.2.0 and the new beta 7. Tried the permissions but there is still a problem, actually 2 problems.

  1. permissions not working

jadestorm,

just to make things clear in regards to your question:

" is nothing in your gatewayRestrictions table? "

The only thing I have set and the way i understand the gateway pages in the admin area is as follows

Page “Gateway Settings”

  1. I checkmarked MSN

  2. opened the “Permission tab”

  3. choose “These users can register”

  4. entered user with his name only

  5. hit “Save Permissions”

After this setting, this particular user is not able to connect to MSN as he gets this Server 400 error which I mentioned earlier in the beta 6a version. And this is the way I understand the GUI to set permissions for users/groups to specific transports. Am I wrong here and am I missing steps ?

Changing the setting in step 3 to “All user can register” the user is able to connect just fine to the transport and has his full contact list of this transport in the jabber client (Pandion).

The other page “Gateway Registrations” looks for me, that I have to setup a user which hasn’'t an account at a specific transport and through this setup (Registration) he is able to contact this particular transport and registers with it (first time ?)

turbo

And I was telling you before that I can’‘t reproduce the 400 error. Unless you can see some sort of logs or something that’‘s a result of this error, or something I can do that can reproduce it, there’‘s not much I can do. Maybe looking in the admin-console logs or turning on “jetty debug”… I think it’'s a system property of jetty.debug.enable

jadestorm,

I just wanted to make sure that I am doing the correct steps. For sure, I will lookup the logs and will find the debug option to turn on. Without any logs no handle to fix.

turbo

PS. do you want the logs emailed or here posted ?

Either way works =)

jadestorm

email is on the way.

turbo

jadestorm,

as I got just the mail back as the mx for rr were not reachable, I will post it here. It’'s propably ugly, but…

I am using the internal database. This wasn’'t mentioned in the findings. So here it goes:

wildfire 3.2.0

Logs were all cleared before starting test.

  1. Connecting to transport MSN with permission setting to “All users can register”.

Error Log, info log, warn log empty, no entries.

Debug log has the following entries in 11 lines


2007.02.11 12:46:46 No AuthorizationProvider’'s found. Loading DefaultAuthorizationPolicy

2007.02.11 12:46:46 jenny authorized to jenny

2007.02.11 12:46:46 msn: rosterLoaded jenny

2007.02.11 12:46:46 Received iq packet:


Before starting second test, all logs were deleted. Logs were empty !

  1. Test Connecting to transport MSN with permissions set to " These users can register" using the plain user name

Error log empty, info log empty

Warn log has following entries, 2 lines


2007.02.11 12:55:01 Missing type info for savePermissions(2 in dwr.xml


debug log has following entries, 13 lines


2007.02.11 12:54:53 Sending 304 for /engine.js

2007.02.11 12:54:53 Sending 304 for /util.js

2007.02.11 12:55:01 Known extra type info:

2007.02.11 12:55:01 Known extra type info:

2007.02.11 12:55:01 Exec[0]: ConfigManager.savePermissions()

2007.02.11 12:55:01 --Object created, not stored. Call params (string:msn, number:2, Array:[reference:c0-e1], Array:[reference:c0-e2]) id=3713_1171220101092. Using (XHR,POST)

2007.02.11 12:55:01 Returning: id[3713_1171220101092] assign[s0] xhr[true]

2007.02.11 12:55:01 var s0=[];

DWREngine._handleResponse(’‘3713_1171220101092’’, s0);

2007.02.11 12:55:38 Received iq packet:


The message of the last line is not showing to the user in the client. It is only showing : Server error code 400

turbo

Oh ok, this makes a -lot- more sense now. =) All this time I thought you were getting error code 400 from your web browser. Anyway, it looks like the client is not properly showing the message of type error. I’‘m not sure why it would not be doing that. I’‘ve run into a couple of clients here and there though that ignore some message types (sigh)… like headline is a big one that gets ignored. It’‘s possible that pandion is ignoring the message. For all practical purposes, if you see it there in the logs, it should have gone on through Wildfire to the user’'s client unless Wildfire itself bricked it somewhere. Also those messages you are seeing about:

2007.02.11 12:55:01 Missing type info for savePermissions(3 in dwr.xml

Are ignorable. They are just due to some misconfigurations I apparently have in DWR. Nothing that actually effects functionality.

To clarify what’'s not working …

Go to the permissions panel, set a couple of users to have permission, save, and then leave that screen and come back (basically you want it to load fresh from the server) After you do that, let me know if you still see the people that you entered listed in the permissions list.

Hey good news, I was just able to duplicate your issue! Not entirely sure why I wasn’‘t before. Seems to have to do with what JID I was trying from. Either way, I’'ve got something to work with now! GATE-181

Good lord. Twas an easy one to fix too. Thanks for your patience!

jadestorm,

I am happy that I could help out. Patience, for sure. That’‘s why it’'s beta , hey

One should have patience !

Anyways, may I ask for a favour ? As 3.2.0 is not stable yet and I am for the next time stuck with the stable 3.1.1, would it be to much ask if you could fix this for the beta 6 too, so I could use it with 3.1.1 ? It was the exact same error.

turbo

Well… normally I would say yes but my free time is very limited and there’‘s a lot of misc tweaks I’‘d have to do to recompile the old versions. 3.2.1 is supposed to be coming out real soon now so ideally I’‘d like to wait for that to come out so we can see if the big issues are fixed. If it’'s still a mess, and I have some free time, I might give it a show. For now, lets see how 3.2.1 does.

ok, lets wait and see.

turbo