[SOGo] Not all contacs are synced when using baikal, lightning, and sogo connector
Hello while using the combination mentioned above (lighting 2.6.1, baikal 0.26, sogo connector 24.0.1) the basic communication works flawlessly. But only 178 of my 298 contacts are synchronised. I can't find any hints in the apache log. Any ideas about the problem? Any solution proposals? janus -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Password change behavior
Can someone please fill me in on the expected behavior of SOGo after the user changes their password through preferences? My users, who can change their passwords just fine through the preferences, get stuck in SOGo after changing the password. It appears as if they are still logged in, but if they go to write a new message or click on a different feature (such as Calendar), they are presented with a login box. (At this point, they can log in fine using their new password.) I want to confirm that this is by design, or if there is something I need to look into. It seems that either the user should not have to relog in at all, or that the user should immediately be logged off and presented with a new login screen. Thanks for any help. ~Laz-- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Password change behavior
I might add that the behavior I see in Safari works as I would expect — changing password simply changes password and leaves all other functions working as they were, including SOGo, email and calendar. FireFox, on the other hand, exhibits the behavior where the authentication gets broken and the website does not display or operate properly until user logs back in. Thanks for any help. ~Laz On Nov 20, 2013, at 1:16 PM, Laz C. Peterson l...@paravis.net wrote: Can someone please fill me in on the expected behavior of SOGo after the user changes their password through preferences? My users, who can change their passwords just fine through the preferences, get stuck in SOGo after changing the password. It appears as if they are still logged in, but if they go to write a new message or click on a different feature (such as Calendar), they are presented with a login box. (At this point, they can log in fine using their new password.) I want to confirm that this is by design, or if there is something I need to look into. It seems that either the user should not have to relog in at all, or that the user should immediately be logged off and presented with a new login screen. Thanks for any help. ~Laz-- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Password change behavior
Jean, So I went to another computer of mine and tried both FireFox and Safari (sorry, no Windows systems here!) and neither worked properly. On my workstation, FireFox does not work, and in further testing, I noticed that Safari did not actually work every time. So I tried a little troubleshooting ... I changed my password and stayed in the “Preferences” screen for a little while before clicking out. If I stay for a little while without clicking, it seems to work! If I close out almost immediately after and try doing other things, I get an error message something like object not found: lpeter...@myemaildomain.com = Mail = 0 = compose”. I do have “SOGoCacheCleanupInterval” set to 10, if that makes any difference. Attached is the SOGo debug log when it does not work and the SOGo debug log when it does. I honestly don’t know the difference of what we’re looking at there. Maybe I can try and get some better-looking logs for you, just let me know how. Also, the latency and connection between all of the servers is great (0.3ms average) … Thanks again Jean. ~Laz -- users@sogo.nu https://inverse.ca/sogo/lists sogo.log-broken Description: Binary data sogo.log-working Description: Binary data On Nov 20, 2013, at 2:14 PM, Jean Raby jr...@inverse.ca wrote: On 13-11-20 4:16 PM, Laz C. Peterson wrote: Can someone please fill me in on the expected behavior of SOGo after the user changes their password through preferences? My users, who can change their passwords just fine through the preferences, get stuck in SOGo after changing the password. It appears as if they are still logged in, but if they go to write a new message or click on a different feature (such as Calendar), they are presented with a login box. (At this point, they can log in fine using their new password.) I want to confirm that this is by design, or if there is something I need to look into. It seems that either the user should not have to relog in at all, or that the user should immediately be logged off and presented with a new login screen. Can you explain or post your sogo configuration? Anything relevant in the logs? I just tested this with sogo using openldap as its auth backend and it works as designed. That is: when I change my password, I can still use sogo without having to log back in. Thanks for any help. ~Laz-- -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Password change behavior
Jean, hello. You are correct, it does work just fine as you have designed. Which browser are you using? There was nothing abnormal in the logs, neither on the LDAP server nor the SOGo server. All looks good. This is not debug logging, however. Maybe you can try reproducing the problem. I have been primarily using FireFox lately, which is the browser that is not acting properly. After I sent my initial message, I decided to try Safari just for fun, and that worked *perfectly*. If you don’t use FireFox, would you mind trying that out and see if you get the same result? I’m a little confused as to why it would act that way. Possibly it is an issue on my specific workstation’s install of FireFox? Thanks for your response. Please let me know if there is any more information I can get for you. ~Laz On Nov 20, 2013, at 2:14 PM, Jean Raby jr...@inverse.ca wrote: On 13-11-20 4:16 PM, Laz C. Peterson wrote: Can someone please fill me in on the expected behavior of SOGo after the user changes their password through preferences? My users, who can change their passwords just fine through the preferences, get stuck in SOGo after changing the password. It appears as if they are still logged in, but if they go to write a new message or click on a different feature (such as Calendar), they are presented with a login box. (At this point, they can log in fine using their new password.) I want to confirm that this is by design, or if there is something I need to look into. It seems that either the user should not have to relog in at all, or that the user should immediately be logged off and presented with a new login screen. Can you explain or post your sogo configuration? Anything relevant in the logs? I just tested this with sogo using openldap as its auth backend and it works as designed. That is: when I change my password, I can still use sogo without having to log back in. Thanks for any help. ~Laz-- -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Password change behavior
On 13-11-20 7:55 PM, Laz C. Peterson wrote: I do have “SOGoCacheCleanupInterval” set to 10, if that makes any difference. Why is the cleanup interval set so low? It should work anyway, but I'm curious. Also, for the record, I was testing with chrome. (with the default cache cleanup interval: 300) -- users@sogo.nu https://inverse.ca/sogo/lists
