[sip-comm-dev] Jabber contact presence authorization


#1

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
             Contact B accept the Authorization request
             User A receive a confermation that B has accepted the request.
             User A can see the presence status of user B
             User B cannot see the presence status of user A
             Only User B is Auhorized for User A, but User A is not
             authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
                        Contact B accept the Auhtorization request
                        User A receive a confermation that B has accepted.
                        User A can see the presence status of User B
                        User B can see the presence status of User A
                        Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
                              Add a Jabber account user "B" on PC-2
                              From User A add a new Jabber Contact "User B"
                              On PC-2 User B accept the Authorization request.
                              ON PC-1 User A acknowladge the accept of User B

                              You will see now that User B cannot see the
                              presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

···

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
Contact B accept the Authorization request
User A receive a confermation that B has accepted the request.
User A can see the presence status of user B
User B cannot see the presence status of user A
Only User B is Auhorized for User A, but User A is not
authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
Contact B accept the Auhtorization request
User A receive a confermation that B has accepted.
User A can see the presence status of User B
User B can see the presence status of User A
Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
Add a Jabber account user "B" on PC-2
From User A add a new Jabber Contact "User B"
On PC-2 User B accept the Authorization request.
ON PC-1 User A acknowladge the accept of User B

                         You will see now that User B cannot see the
                         presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi

···

Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
            Contact B accept the Authorization request
            User A receive a confermation that B has accepted the request.
            User A can see the presence status of user B
            User B cannot see the presence status of user A
            Only User B is Auhorized for User A, but User A is not
            authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
                       Contact B accept the Auhtorization request
                       User A receive a confermation that B has accepted.
                       User A can see the presence status of User B
                       User B can see the presence status of User A
                       Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
                             Add a Jabber account user "B" on PC-2
                             From User A add a new Jabber Contact "User B"
                             On PC-2 User B accept the Authorization request.
                             ON PC-1 User A acknowladge the accept of User B

                             You will see now that User B cannot see the
                             presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

···

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
Contact B accept the Authorization request
User A receive a confermation that B has accepted the request.
User A can see the presence status of user B
User B cannot see the presence status of user A
Only User B is Auhorized for User A, but User A is not
authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
Contact B accept the Auhtorization request
User A receive a confermation that B has accepted.
User A can see the presence status of User B
User B can see the presence status of User A
Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
Add a Jabber account user "B" on PC-2
From User A add a new Jabber Contact "User B"
On PC-2 User B accept the Authorization request.
ON PC-1 User A acknowladge the accept of User B

                         You will see now that User B cannot see the
                         presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hi Damencho,

sorry if i get back on the topic, is there any chances to resolve the issue of the 2 way presence subscription for Jabber account ?
I just try to add contact on SC using Gtalk account and it works fine, can we reproduce the same behievior ? Gtalk is also a Jabber account but subscription is set as 2 way.

Thanks again for your kind help

Fabio galdi

···

Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
            Contact B accept the Authorization request
            User A receive a confermation that B has accepted the request.
            User A can see the presence status of user B
            User B cannot see the presence status of user A
            Only User B is Auhorized for User A, but User A is not
            authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
                       Contact B accept the Auhtorization request
                       User A receive a confermation that B has accepted.
                       User A can see the presence status of User B
                       User B can see the presence status of User A
                       Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
                             Add a Jabber account user "B" on PC-2
                             From User A add a new Jabber Contact "User B"
                             On PC-2 User B accept the Authorization request.
                             ON PC-1 User A acknowladge the accept of User B

                             You will see now that User B cannot see the
                             presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi

···

Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
           Contact B accept the Authorization request
           User A receive a confermation that B has accepted the request.
           User A can see the presence status of user B
           User B cannot see the presence status of user A
           Only User B is Auhorized for User A, but User A is not
           authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
                      Contact B accept the Auhtorization request
                      User A receive a confermation that B has accepted.
                      User A can see the presence status of User B
                      User B can see the presence status of User A
                      Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
                            Add a Jabber account user "B" on PC-2
                            From User A add a new Jabber Contact "User B"
                            On PC-2 User B accept the Authorization request.
                            ON PC-1 User A acknowladge the accept of User B

                            You will see now that User B cannot see the
                            presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#7

Hi Damencho,

Can i suggest to put the buddy in the official list directly and not in the "Not in contact list" Group ? why you want to let the users to perform an additional operation to move the contact from one group to another? i mean in the real life scenario with all the IM software the auth is alway both with a single action, look at gtalk, skype, msn and all the major.

Let me have your comment

Regards
Fabio Galdi

···

Il giorno 18/ott/2010, alle ore 13.16, Damian Minkov ha scritto:

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
            Contact B accept the Authorization request
            User A receive a confermation that B has accepted the request.
            User A can see the presence status of user B
            User B cannot see the presence status of user A
            Only User B is Auhorized for User A, but User A is not
            authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
                       Contact B accept the Auhtorization request
                       User A receive a confermation that B has accepted.
                       User A can see the presence status of User B
                       User B can see the presence status of User A
                       Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
                             Add a Jabber account user "B" on PC-2
                             From User A add a new Jabber Contact "User B"
                             On PC-2 User B accept the Authorization request.
                             ON PC-1 User A acknowladge the accept of User B

                             You will see now that User B cannot see the
                             presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#8

Hi,

maybe its because the user can move the contact to the desired group.
In other words when the initial authorization is received which group
should we choose to add the contact to.
This way the user can just drag and drop the contact to the group he
wants or just move it using the context menu.

Regards
damencho

···

On Mon, Oct 18, 2010 at 2:37 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

Can i suggest to put the buddy in the official list directly and not in the "Not in contact list" Group ? why you want to let the users to perform an additional operation to move the contact from one group to another? i mean in the real life scenario with all the IM software the auth is alway both with a single action, look at gtalk, skype, msn and all the major.

Let me have your comment

Regards
Fabio Galdi

Il giorno 18/ott/2010, alle ore 13.16, Damian Minkov ha scritto:

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
Contact B accept the Authorization request
User A receive a confermation that B has accepted the request.
User A can see the presence status of user B
User B cannot see the presence status of user A
Only User B is Auhorized for User A, but User A is not
authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
Contact B accept the Auhtorization request
User A receive a confermation that B has accepted.
User A can see the presence status of User B
User B can see the presence status of User A
Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
Add a Jabber account user "B" on PC-2
From User A add a new Jabber Contact "User B"
On PC-2 User B accept the Authorization request.
ON PC-1 User A acknowladge the accept of User B

                         You will see now that User B cannot see the
                         presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#9

Hi Damian,

It is ok to let the buddy in the "Not in contact List" in this case, but at least authorize him in order to view the presence before he move to any other group. Or i did not understand well ? the authorization will be perform only when moved to another group ?

Thanks
Fabio

···

Il giorno 18/ott/2010, alle ore 13.59, Damian Minkov ha scritto:

Hi,

maybe its because the user can move the contact to the desired group.
In other words when the initial authorization is received which group
should we choose to add the contact to.
This way the user can just drag and drop the contact to the group he
wants or just move it using the context menu.

Regards
damencho

On Mon, Oct 18, 2010 at 2:37 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

Can i suggest to put the buddy in the official list directly and not in the "Not in contact list" Group ? why you want to let the users to perform an additional operation to move the contact from one group to another? i mean in the real life scenario with all the IM software the auth is alway both with a single action, look at gtalk, skype, msn and all the major.

Let me have your comment

Regards
Fabio Galdi

Il giorno 18/ott/2010, alle ore 13.16, Damian Minkov ha scritto:

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
            Contact B accept the Authorization request
            User A receive a confermation that B has accepted the request.
            User A can see the presence status of user B
            User B cannot see the presence status of user A
            Only User B is Auhorized for User A, but User A is not
            authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
                       Contact B accept the Auhtorization request
                       User A receive a confermation that B has accepted.
                       User A can see the presence status of User B
                       User B can see the presence status of User A
                       Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
                             Add a Jabber account user "B" on PC-2
                             From User A add a new Jabber Contact "User B"
                             On PC-2 User B accept the Authorization request.
                             ON PC-1 User A acknowladge the accept of User B

                             You will see now that User B cannot see the
                             presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#10

Yes, authorization is performed when added to the contact list, moving
from not in contact list to a group in the contact list is another way
to add a contact to our list.

Cheers
damencho

···

On Mon, Oct 18, 2010 at 3:08 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damian,

It is ok to let the buddy in the "Not in contact List" in this case, but at least authorize him in order to view the presence before he move to any other group. Or i did not understand well ? the authorization will be perform only when moved to another group ?

Thanks
Fabio

Il giorno 18/ott/2010, alle ore 13.59, Damian Minkov ha scritto:

Hi,

maybe its because the user can move the contact to the desired group.
In other words when the initial authorization is received which group
should we choose to add the contact to.
This way the user can just drag and drop the contact to the group he
wants or just move it using the context menu.

Regards
damencho

On Mon, Oct 18, 2010 at 2:37 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

Can i suggest to put the buddy in the official list directly and not in the "Not in contact list" Group ? why you want to let the users to perform an additional operation to move the contact from one group to another? i mean in the real life scenario with all the IM software the auth is alway both with a single action, look at gtalk, skype, msn and all the major.

Let me have your comment

Regards
Fabio Galdi

Il giorno 18/ott/2010, alle ore 13.16, Damian Minkov ha scritto:

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
Contact B accept the Authorization request
User A receive a confermation that B has accepted the request.
User A can see the presence status of user B
User B cannot see the presence status of user A
Only User B is Auhorized for User A, but User A is not
authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
Contact B accept the Auhtorization request
User A receive a confermation that B has accepted.
User A can see the presence status of User B
User B can see the presence status of User A
Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
Add a Jabber account user "B" on PC-2
From User A add a new Jabber Contact "User B"
On PC-2 User B accept the Authorization request.
ON PC-1 User A acknowladge the accept of User B

                         You will see now that User B cannot see the
                         presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#11

Hi,

I've just committed a change(r7831 or build.3017) regarding the
subject we talk about.

Cheers
damencho

···

On Mon, Oct 18, 2010 at 3:14 PM, Damian Minkov <damencho@sip-communicator.org> wrote:

Yes, authorization is performed when added to the contact list, moving
from not in contact list to a group in the contact list is another way
to add a contact to our list.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:08 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damian,

It is ok to let the buddy in the "Not in contact List" in this case, but at least authorize him in order to view the presence before he move to any other group. Or i did not understand well ? the authorization will be perform only when moved to another group ?

Thanks
Fabio

Il giorno 18/ott/2010, alle ore 13.59, Damian Minkov ha scritto:

Hi,

maybe its because the user can move the contact to the desired group.
In other words when the initial authorization is received which group
should we choose to add the contact to.
This way the user can just drag and drop the contact to the group he
wants or just move it using the context menu.

Regards
damencho

On Mon, Oct 18, 2010 at 2:37 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

Can i suggest to put the buddy in the official list directly and not in the "Not in contact list" Group ? why you want to let the users to perform an additional operation to move the contact from one group to another? i mean in the real life scenario with all the IM software the auth is alway both with a single action, look at gtalk, skype, msn and all the major.

Let me have your comment

Regards
Fabio Galdi

Il giorno 18/ott/2010, alle ore 13.16, Damian Minkov ha scritto:

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
Contact B accept the Authorization request
User A receive a confermation that B has accepted the request.
User A can see the presence status of user B
User B cannot see the presence status of user A
Only User B is Auhorized for User A, but User A is not
authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
Contact B accept the Auhtorization request
User A receive a confermation that B has accepted.
User A can see the presence status of User B
User B can see the presence status of User A
Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
Add a Jabber account user "B" on PC-2
From User A add a new Jabber Contact "User B"
On PC-2 User B accept the Authorization request.
ON PC-1 User A acknowladge the accept of User B

                         You will see now that User B cannot see the
                         presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#12

HI Damencho

with build 3017 the contact now is placed in the correct Group "NotinContactList".
But i still belive that from usability point of view this process is still not correct, the behavior is different from all the other IM software and different from what the user is aspecting, when a contact is added or you are added from some one you aspect to see his presence, but now the user have to perform an additional action that is to create a group and move the contact in the group in order to obtain the authorization. put your self in the common user position, we need to write a tutorial just to let them know how to have proper contact list.

Of course is just my opinion but i see the things from users prospective and not developers one.

Thanks again for your comment and feedback.

Fabio Galdi

···

Il giorno 18/ott/2010, alle ore 15.38, Damian Minkov ha scritto:

Hi,

I've just committed a change(r7831 or build.3017) regarding the
subject we talk about.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:14 PM, Damian Minkov > <damencho@sip-communicator.org> wrote:

Yes, authorization is performed when added to the contact list, moving
from not in contact list to a group in the contact list is another way
to add a contact to our list.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:08 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damian,

It is ok to let the buddy in the "Not in contact List" in this case, but at least authorize him in order to view the presence before he move to any other group. Or i did not understand well ? the authorization will be perform only when moved to another group ?

Thanks
Fabio

Il giorno 18/ott/2010, alle ore 13.59, Damian Minkov ha scritto:

Hi,

maybe its because the user can move the contact to the desired group.
In other words when the initial authorization is received which group
should we choose to add the contact to.
This way the user can just drag and drop the contact to the group he
wants or just move it using the context menu.

Regards
damencho

On Mon, Oct 18, 2010 at 2:37 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

Can i suggest to put the buddy in the official list directly and not in the "Not in contact list" Group ? why you want to let the users to perform an additional operation to move the contact from one group to another? i mean in the real life scenario with all the IM software the auth is alway both with a single action, look at gtalk, skype, msn and all the major.

Let me have your comment

Regards
Fabio Galdi

Il giorno 18/ott/2010, alle ore 13.16, Damian Minkov ha scritto:

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
            Contact B accept the Authorization request
            User A receive a confermation that B has accepted the request.
            User A can see the presence status of user B
            User B cannot see the presence status of user A
            Only User B is Auhorized for User A, but User A is not
            authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
                       Contact B accept the Auhtorization request
                       User A receive a confermation that B has accepted.
                       User A can see the presence status of User B
                       User B can see the presence status of User A
                       Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
                             Add a Jabber account user "B" on PC-2
                             From User A add a new Jabber Contact "User B"
                             On PC-2 User B accept the Authorization request.
                             ON PC-1 User A acknowladge the accept of User B

                             You will see now that User B cannot see the
                             presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#13

Hi,

I see what you mean, but all protocols behave this way now and I don't
think that all clients behave like it. I tested today another
multiprotocol client and it behave almost the same as we at the moment
(except that it didn't see the contact after accepting authorization)
and at last, there are some protocols that don't support contacts
without groups, what will be the behavior then? in which group will we
add it?

I understand what you mean and I like the idea. Maybe its a good to
add a checkbox to the authorization dialog which says "Add contact to
list" which will be by default check and will pop up after that the
Add Contact dialog in which most of the data will be filled and where
the user can choose a group.
But I'm not sure how good is to pop so much dialogs one after another.

This feature concerns a lot of changes and changing a long used
behavior so we must hear and other developers opinion :slight_smile:
and after that schedule it in the issue tracker.

Regards
damencho

···

On Mon, Oct 18, 2010 at 6:02 PM, Fabio Telme <fabio@telme.sg> wrote:

HI Damencho

with build 3017 the contact now is placed in the correct Group "NotinContactList".
But i still belive that from usability point of view this process is still not correct, the behavior is different from all the other IM software and different from what the user is aspecting, when a contact is added or you are added from some one you aspect to see his presence, but now the user have to perform an additional action that is to create a group and move the contact in the group in order to obtain the authorization. put your self in the common user position, we need to write a tutorial just to let them know how to have proper contact list.

Of course is just my opinion but i see the things from users prospective and not developers one.

Thanks again for your comment and feedback.

Fabio Galdi

Il giorno 18/ott/2010, alle ore 15.38, Damian Minkov ha scritto:

Hi,

I've just committed a change(r7831 or build.3017) regarding the
subject we talk about.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:14 PM, Damian Minkov >> <damencho@sip-communicator.org> wrote:

Yes, authorization is performed when added to the contact list, moving
from not in contact list to a group in the contact list is another way
to add a contact to our list.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:08 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damian,

It is ok to let the buddy in the "Not in contact List" in this case, but at least authorize him in order to view the presence before he move to any other group. Or i did not understand well ? the authorization will be perform only when moved to another group ?

Thanks
Fabio

Il giorno 18/ott/2010, alle ore 13.59, Damian Minkov ha scritto:

Hi,

maybe its because the user can move the contact to the desired group.
In other words when the initial authorization is received which group
should we choose to add the contact to.
This way the user can just drag and drop the contact to the group he
wants or just move it using the context menu.

Regards
damencho

On Mon, Oct 18, 2010 at 2:37 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

Can i suggest to put the buddy in the official list directly and not in the "Not in contact list" Group ? why you want to let the users to perform an additional operation to move the contact from one group to another? i mean in the real life scenario with all the IM software the auth is alway both with a single action, look at gtalk, skype, msn and all the major.

Let me have your comment

Regards
Fabio Galdi

Il giorno 18/ott/2010, alle ore 13.16, Damian Minkov ha scritto:

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
Contact B accept the Authorization request
User A receive a confermation that B has accepted the request.
User A can see the presence status of user B
User B cannot see the presence status of user A
Only User B is Auhorized for User A, but User A is not
authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
Contact B accept the Auhtorization request
User A receive a confermation that B has accepted.
User A can see the presence status of User B
User B can see the presence status of User A
Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
Add a Jabber account user "B" on PC-2
From User A add a new Jabber Contact "User B"
On PC-2 User B accept the Authorization request.
ON PC-1 User A acknowladge the accept of User B

                         You will see now that User B cannot see the
                         presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#14

In Jabber (and in most IM protocols), we assume that people want
bidirectional presence subscriptions. Yes, you can set up one-way
subscriptions, but it seems to me more useful to automatically request
an outbound subscription when you approve an inbound request.

Peter

···

On 10/18/10 9:58 AM, Fabio Telme wrote:

Hi Damencho,

thanks for the comment, actually i don't think is an issue regarding
Groups, but is how the Authorization process is handled, the
authorization should be generate on both party , i mean when B
accept auth request from A, a new request to A need to be generate at
the same time. I did test with other client like iChat of Apple,
Gtalk, Qutecom, Audium and when the contact B accept the
Authorization from A authomatcly an authorization from B is sent to
contact A, It is just that when B accept A request, a new Request
from B to A need to be generated. So i agree with you could be nice
to hear the opinion also from other developer to understand if we
miss something.

--
Peter Saint-Andre
https://stpeter.im/


#15

Hi Damencho,

thanks for the comment, actually i don't think is an issue regarding Groups, but is how the Authorization process is handled, the authorization should be generate on both party , i mean when B accept auth request from A, a new request to A need to be generate at the same time.
I did test with other client like iChat of Apple, Gtalk, Qutecom, Audium and when the contact B accept the Authorization from A authomatcly an authorization from B is sent to contact A, It is just that when B accept A request, a new Request from B to A need to be generated.
So i agree with you could be nice to hear the opinion also from other developer to understand if we miss something.

Thanks
Fabio Galdi

···

Il giorno 18/ott/2010, alle ore 17.38, Damian Minkov ha scritto:

Hi,

I see what you mean, but all protocols behave this way now and I don't
think that all clients behave like it. I tested today another
multiprotocol client and it behave almost the same as we at the moment
(except that it didn't see the contact after accepting authorization)
and at last, there are some protocols that don't support contacts
without groups, what will be the behavior then? in which group will we
add it?

I understand what you mean and I like the idea. Maybe its a good to
add a checkbox to the authorization dialog which says "Add contact to
list" which will be by default check and will pop up after that the
Add Contact dialog in which most of the data will be filled and where
the user can choose a group.
But I'm not sure how good is to pop so much dialogs one after another.

This feature concerns a lot of changes and changing a long used
behavior so we must hear and other developers opinion :slight_smile:
and after that schedule it in the issue tracker.

Regards
damencho

On Mon, Oct 18, 2010 at 6:02 PM, Fabio Telme <fabio@telme.sg> wrote:

HI Damencho

with build 3017 the contact now is placed in the correct Group "NotinContactList".
But i still belive that from usability point of view this process is still not correct, the behavior is different from all the other IM software and different from what the user is aspecting, when a contact is added or you are added from some one you aspect to see his presence, but now the user have to perform an additional action that is to create a group and move the contact in the group in order to obtain the authorization. put your self in the common user position, we need to write a tutorial just to let them know how to have proper contact list.

Of course is just my opinion but i see the things from users prospective and not developers one.

Thanks again for your comment and feedback.

Fabio Galdi

Il giorno 18/ott/2010, alle ore 15.38, Damian Minkov ha scritto:

Hi,

I've just committed a change(r7831 or build.3017) regarding the
subject we talk about.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:14 PM, Damian Minkov >>> <damencho@sip-communicator.org> wrote:

Yes, authorization is performed when added to the contact list, moving
from not in contact list to a group in the contact list is another way
to add a contact to our list.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:08 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damian,

It is ok to let the buddy in the "Not in contact List" in this case, but at least authorize him in order to view the presence before he move to any other group. Or i did not understand well ? the authorization will be perform only when moved to another group ?

Thanks
Fabio

Il giorno 18/ott/2010, alle ore 13.59, Damian Minkov ha scritto:

Hi,

maybe its because the user can move the contact to the desired group.
In other words when the initial authorization is received which group
should we choose to add the contact to.
This way the user can just drag and drop the contact to the group he
wants or just move it using the context menu.

Regards
damencho

On Mon, Oct 18, 2010 at 2:37 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

Can i suggest to put the buddy in the official list directly and not in the "Not in contact list" Group ? why you want to let the users to perform an additional operation to move the contact from one group to another? i mean in the real life scenario with all the IM software the auth is alway both with a single action, look at gtalk, skype, msn and all the major.

Let me have your comment

Regards
Fabio Galdi

Il giorno 18/ott/2010, alle ore 13.16, Damian Minkov ha scritto:

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
            Contact B accept the Authorization request
            User A receive a confermation that B has accepted the request.
            User A can see the presence status of user B
            User B cannot see the presence status of user A
            Only User B is Auhorized for User A, but User A is not
            authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
                       Contact B accept the Auhtorization request
                       User A receive a confermation that B has accepted.
                       User A can see the presence status of User B
                       User B can see the presence status of User A
                       Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
                             Add a Jabber account user "B" on PC-2
                             From User A add a new Jabber Contact "User B"
                             On PC-2 User B accept the Authorization request.
                             ON PC-1 User A acknowladge the accept of User B

                             You will see now that User B cannot see the
                             presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#16

Hi Peter,

Yes this is exactly what i would like to bring to the attention and make the necessary modification if possible.

Thanks
Fabio Galdi

···

Il giorno 18/ott/2010, alle ore 18.38, Peter Saint-Andre ha scritto:

On 10/18/10 9:58 AM, Fabio Telme wrote:

Hi Damencho,

thanks for the comment, actually i don't think is an issue regarding
Groups, but is how the Authorization process is handled, the
authorization should be generate on both party , i mean when B
accept auth request from A, a new request to A need to be generate at
the same time. I did test with other client like iChat of Apple,
Gtalk, Qutecom, Audium and when the contact B accept the
Authorization from A authomatcly an authorization from B is sent to
contact A, It is just that when B accept A request, a new Request
from B to A need to be generated. So i agree with you could be nice
to hear the opinion also from other developer to understand if we
miss something.

In Jabber (and in most IM protocols), we assume that people want
bidirectional presence subscriptions. Yes, you can set up one-way
subscriptions, but it seems to me more useful to automatically request
an outbound subscription when you approve an inbound request.

Peter

--
Peter Saint-Andre
https://stpeter.im/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#17

Hi,

I see, you talk about authorization request, and yes I think it from
developer perspective :slight_smile: and that's why I talk about groups and adding
to groups. Cause most of the protocols generate authorization request
after you have added the contact to your list.

Cheers
damencho

···

On Mon, Oct 18, 2010 at 6:58 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

thanks for the comment, actually i don't think is an issue regarding Groups, but is how the Authorization process is handled, the authorization should be generate on both party , i mean when B accept auth request from A, a new request to A need to be generate at the same time.
I did test with other client like iChat of Apple, Gtalk, Qutecom, Audium and when the contact B accept the Authorization from A authomatcly an authorization from B is sent to contact A, It is just that when B accept A request, a new Request from B to A need to be generated.
So i agree with you could be nice to hear the opinion also from other developer to understand if we miss something.

Thanks
Fabio Galdi

Il giorno 18/ott/2010, alle ore 17.38, Damian Minkov ha scritto:

Hi,

I see what you mean, but all protocols behave this way now and I don't
think that all clients behave like it. I tested today another
multiprotocol client and it behave almost the same as we at the moment
(except that it didn't see the contact after accepting authorization)
and at last, there are some protocols that don't support contacts
without groups, what will be the behavior then? in which group will we
add it?

I understand what you mean and I like the idea. Maybe its a good to
add a checkbox to the authorization dialog which says "Add contact to
list" which will be by default check and will pop up after that the
Add Contact dialog in which most of the data will be filled and where
the user can choose a group.
But I'm not sure how good is to pop so much dialogs one after another.

This feature concerns a lot of changes and changing a long used
behavior so we must hear and other developers opinion :slight_smile:
and after that schedule it in the issue tracker.

Regards
damencho

On Mon, Oct 18, 2010 at 6:02 PM, Fabio Telme <fabio@telme.sg> wrote:

HI Damencho

with build 3017 the contact now is placed in the correct Group "NotinContactList".
But i still belive that from usability point of view this process is still not correct, the behavior is different from all the other IM software and different from what the user is aspecting, when a contact is added or you are added from some one you aspect to see his presence, but now the user have to perform an additional action that is to create a group and move the contact in the group in order to obtain the authorization. put your self in the common user position, we need to write a tutorial just to let them know how to have proper contact list.

Of course is just my opinion but i see the things from users prospective and not developers one.

Thanks again for your comment and feedback.

Fabio Galdi

Il giorno 18/ott/2010, alle ore 15.38, Damian Minkov ha scritto:

Hi,

I've just committed a change(r7831 or build.3017) regarding the
subject we talk about.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:14 PM, Damian Minkov >>>> <damencho@sip-communicator.org> wrote:

Yes, authorization is performed when added to the contact list, moving
from not in contact list to a group in the contact list is another way
to add a contact to our list.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:08 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damian,

It is ok to let the buddy in the "Not in contact List" in this case, but at least authorize him in order to view the presence before he move to any other group. Or i did not understand well ? the authorization will be perform only when moved to another group ?

Thanks
Fabio

Il giorno 18/ott/2010, alle ore 13.59, Damian Minkov ha scritto:

Hi,

maybe its because the user can move the contact to the desired group.
In other words when the initial authorization is received which group
should we choose to add the contact to.
This way the user can just drag and drop the contact to the group he
wants or just move it using the context menu.

Regards
damencho

On Mon, Oct 18, 2010 at 2:37 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

Can i suggest to put the buddy in the official list directly and not in the "Not in contact list" Group ? why you want to let the users to perform an additional operation to move the contact from one group to another? i mean in the real life scenario with all the IM software the auth is alway both with a single action, look at gtalk, skype, msn and all the major.

Let me have your comment

Regards
Fabio Galdi

Il giorno 18/ott/2010, alle ore 13.16, Damian Minkov ha scritto:

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
Contact B accept the Authorization request
User A receive a confermation that B has accepted the request.
User A can see the presence status of user B
User B cannot see the presence status of user A
Only User B is Auhorized for User A, but User A is not
authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
Contact B accept the Auhtorization request
User A receive a confermation that B has accepted.
User A can see the presence status of User B
User B can see the presence status of User A
Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
Add a Jabber account user "B" on PC-2
From User A add a new Jabber Contact "User B"
On PC-2 User B accept the Authorization request.
ON PC-1 User A acknowladge the accept of User B

                         You will see now that User B cannot see the
                         presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#18

Hi

Ok i see now, your proposal to move the contact to a Group was just to generate a new auth request for the other party and so have both authoirzed. :slight_smile:

My my request is , if there is a way to make an authorization type "Both" , so that when user add a contact in his list both users are authorized without further action like all the IM client use to do.

So A request Auth to B, B accept and immediatly generate a request to A

That's all :slight_smile:

Thanks
Fabio

···

Il giorno 18/ott/2010, alle ore 18.04, Damian Minkov ha scritto:

Hi,

I see, you talk about authorization request, and yes I think it from
developer perspective :slight_smile: and that's why I talk about groups and adding
to groups. Cause most of the protocols generate authorization request
after you have added the contact to your list.

Cheers
damencho

On Mon, Oct 18, 2010 at 6:58 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

thanks for the comment, actually i don't think is an issue regarding Groups, but is how the Authorization process is handled, the authorization should be generate on both party , i mean when B accept auth request from A, a new request to A need to be generate at the same time.
I did test with other client like iChat of Apple, Gtalk, Qutecom, Audium and when the contact B accept the Authorization from A authomatcly an authorization from B is sent to contact A, It is just that when B accept A request, a new Request from B to A need to be generated.
So i agree with you could be nice to hear the opinion also from other developer to understand if we miss something.

Thanks
Fabio Galdi

Il giorno 18/ott/2010, alle ore 17.38, Damian Minkov ha scritto:

Hi,

I see what you mean, but all protocols behave this way now and I don't
think that all clients behave like it. I tested today another
multiprotocol client and it behave almost the same as we at the moment
(except that it didn't see the contact after accepting authorization)
and at last, there are some protocols that don't support contacts
without groups, what will be the behavior then? in which group will we
add it?

I understand what you mean and I like the idea. Maybe its a good to
add a checkbox to the authorization dialog which says "Add contact to
list" which will be by default check and will pop up after that the
Add Contact dialog in which most of the data will be filled and where
the user can choose a group.
But I'm not sure how good is to pop so much dialogs one after another.

This feature concerns a lot of changes and changing a long used
behavior so we must hear and other developers opinion :slight_smile:
and after that schedule it in the issue tracker.

Regards
damencho

On Mon, Oct 18, 2010 at 6:02 PM, Fabio Telme <fabio@telme.sg> wrote:

HI Damencho

with build 3017 the contact now is placed in the correct Group "NotinContactList".
But i still belive that from usability point of view this process is still not correct, the behavior is different from all the other IM software and different from what the user is aspecting, when a contact is added or you are added from some one you aspect to see his presence, but now the user have to perform an additional action that is to create a group and move the contact in the group in order to obtain the authorization. put your self in the common user position, we need to write a tutorial just to let them know how to have proper contact list.

Of course is just my opinion but i see the things from users prospective and not developers one.

Thanks again for your comment and feedback.

Fabio Galdi

Il giorno 18/ott/2010, alle ore 15.38, Damian Minkov ha scritto:

Hi,

I've just committed a change(r7831 or build.3017) regarding the
subject we talk about.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:14 PM, Damian Minkov >>>>> <damencho@sip-communicator.org> wrote:

Yes, authorization is performed when added to the contact list, moving
from not in contact list to a group in the contact list is another way
to add a contact to our list.

Cheers
damencho

On Mon, Oct 18, 2010 at 3:08 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damian,

It is ok to let the buddy in the "Not in contact List" in this case, but at least authorize him in order to view the presence before he move to any other group. Or i did not understand well ? the authorization will be perform only when moved to another group ?

Thanks
Fabio

Il giorno 18/ott/2010, alle ore 13.59, Damian Minkov ha scritto:

Hi,

maybe its because the user can move the contact to the desired group.
In other words when the initial authorization is received which group
should we choose to add the contact to.
This way the user can just drag and drop the contact to the group he
wants or just move it using the context menu.

Regards
damencho

On Mon, Oct 18, 2010 at 2:37 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

Can i suggest to put the buddy in the official list directly and not in the "Not in contact list" Group ? why you want to let the users to perform an additional operation to move the contact from one group to another? i mean in the real life scenario with all the IM software the auth is alway both with a single action, look at gtalk, skype, msn and all the major.

Let me have your comment

Regards
Fabio Galdi

Il giorno 18/ott/2010, alle ore 13.16, Damian Minkov ha scritto:

Hi,

actually there is a problem and I'm looking at it right now. The
authorization is not 2 way, that's and the reason of existence in
jabber of subscription types like to, from, both and none.
After approving the authorization request, User B must see User A only
under Not in contact list group, and then will be able to add it and
so the other way authorization process will be triggered. But the
problem now is that contact is added to the list and I'm looking at it
now why.

Regards
damencho

On Mon, Oct 18, 2010 at 12:30 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Damencho,

The buddy B has correctly the user A in the list but cannot see its presence, but user A see the presence of user B.
The behiavior is not correct because the Authorization has to happen in two way. A can see B and B can see A.
In order to make B to see A presence i 've to remove the account in the contact list and add gaian starting from B add A in this case also B obtain an authorization from A and they can see each other. But do you agree with me that it is not correct ? i use other Jabber clients, and the authorization always happen in 2 way and not oneway, so i belive there is a bug in this process.

Please let me know

regards
Fabio Galdi
Il giorno 18/ott/2010, alle ore 11.21, Damian Minkov ha scritto:

Hi,

what I see of the scenario you describe is that user B don't have user
A in the contactlist so its normal to not see its presence, cause
hasn't subscribed for it. WDYT?
In this scenario I think that user B will have user A in his contact
list under the group "Not in Contact List". If he move it from there
or just add user A he will start seeing its status. Am I correct?

Regards
damencho

On Mon, Oct 18, 2010 at 12:07 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi

I'm not sure this is the correct channel, i trying to make Jabber protocol to work correctly with Sip-communicator, but i fund a serious issue on the presence authorization process, when a user add a new buddy, it request for authorization to view the presence, but the authorization only happen in one-way, the buddy that has recieved the autorization is auhtorized for the requester, but the requester is not authorized for him. here an explanation.
Is there anybody can look at this issue on the Jabber client authorization process ?

Creating a Jabber account based on "OpenFire" Server, there is an issue in the
Authorization process when adding a new Jabber Contact.

What i do : Jabber user A add a new Jabber Contact B in his list.
What i see : Contact B receive the Authorization request from user A
            Contact B accept the Authorization request
            User A receive a confermation that B has accepted the request.
            User A can see the presence status of user B
            User B cannot see the presence status of user A
            Only User B is Auhorized for User A, but User A is not
            authorized for user B

What i aspect to see : Contact B receive the Authorization request from user A
                       Contact B accept the Auhtorization request
                       User A receive a confermation that B has accepted.
                       User A can see the presence status of User B
                       User B can see the presence status of User A
                       Both users are authorized each other.

How to replicate the issue : Add a Jabber account user "A" on PC-1
                             Add a Jabber account user "B" on PC-2
                             From User A add a new Jabber Contact "User B"
                             On PC-2 User B accept the Authorization request.
                             ON PC-1 User A acknowladge the accept of User B

                             You will see now that User B cannot see the
                             presence status of User A

To confirm that user has one-way authorization problem, it is possible to remove
the contact user B from User A account, and make the Authorization process the
otherway round, User B add jabber contact user A. After that Authorization is
made for both user and the presence work on both way.

It is first time i file an issue so apologise for the format :slight_smile:

Regards
Fabio Galdi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#19

Hi,

yep, I got an Idea :wink: I will test it tomorrow morning and will report it.

Thanks
damencho

···

On Mon, Oct 18, 2010 at 7:45 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Peter,

Yes this is exactly what i would like to bring to the attention and make the necessary modification if possible.

Thanks
Fabio Galdi

Il giorno 18/ott/2010, alle ore 18.38, Peter Saint-Andre ha scritto:

On 10/18/10 9:58 AM, Fabio Telme wrote:

Hi Damencho,

thanks for the comment, actually i don't think is an issue regarding
Groups, but is how the Authorization process is handled, the
authorization should be generate on both party , i mean when B
accept auth request from A, a new request to A need to be generate at
the same time. I did test with other client like iChat of Apple,
Gtalk, Qutecom, Audium and when the contact B accept the
Authorization from A authomatcly an authorization from B is sent to
contact A, It is just that when B accept A request, a new Request
from B to A need to be generated. So i agree with you could be nice
to hear the opinion also from other developer to understand if we
miss something.

In Jabber (and in most IM protocols), we assume that people want
bidirectional presence subscriptions. Yes, you can set up one-way
subscriptions, but it seems to me more useful to automatically request
an outbound subscription when you approve an inbound request.

Peter

--
Peter Saint-Andre
https://stpeter.im/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#20

Hi,

I've tested initiating authorization request when such is received.
The changes pass all current tests.
It triggers a move of the contact to the root group (there is an issue
here as also a presence event comes at the same time and the contact
can be seen twice). Also there is some more work to be done cause on
the side where the first subscription request is created the user sees
too many popups: one that asks for a subscription from the other side,
one for confirmation for initial subscription and one for confirmation
the he was added to others contact list.
I have patch if some one is interested to test or fix the rest of the
issues :slight_smile: and still to hear others opinion :slight_smile:

Cheers
damencho

···

On Mon, Oct 18, 2010 at 7:49 PM, Damian Minkov <damencho@sip-communicator.org> wrote:

Hi,

yep, I got an Idea :wink: I will test it tomorrow morning and will report it.

Thanks
damencho

On Mon, Oct 18, 2010 at 7:45 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Peter,

Yes this is exactly what i would like to bring to the attention and make the necessary modification if possible.

Thanks
Fabio Galdi

Il giorno 18/ott/2010, alle ore 18.38, Peter Saint-Andre ha scritto:

On 10/18/10 9:58 AM, Fabio Telme wrote:

Hi Damencho,

thanks for the comment, actually i don't think is an issue regarding
Groups, but is how the Authorization process is handled, the
authorization should be generate on both party , i mean when B
accept auth request from A, a new request to A need to be generate at
the same time. I did test with other client like iChat of Apple,
Gtalk, Qutecom, Audium and when the contact B accept the
Authorization from A authomatcly an authorization from B is sent to
contact A, It is just that when B accept A request, a new Request
from B to A need to be generated. So i agree with you could be nice
to hear the opinion also from other developer to understand if we
miss something.

In Jabber (and in most IM protocols), we assume that people want
bidirectional presence subscriptions. Yes, you can set up one-way
subscriptions, but it seems to me more useful to automatically request
an outbound subscription when you approve an inbound request.

Peter

--
Peter Saint-Andre
https://stpeter.im/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net