Service administration

Discussion:

Fernando Tapia Rico

2012-01-18 09:45:05 UTC

Hi all,
I just started using xmpp4r, so it could be a newbie question. I wonder if there is a way to handle users, their rosters and their info. All of these tasks should be done using the admin account:

- Create/Register an user (I found jabber:iq:register)
- Delete an user
- Update user information (I saw xmpp4r can update user information, but it should be done from the current user's account, not from admin)
- Add a user to another user's roster
- Delete a user from another user's roster

I saw Openfire Browser administration let me do this, but I'm not sure if it's an internal API or part of the XMPP protocol.
Thanks in advance
Cheers

--
Fernando Tapia Rico
http://fernandotapiarico.com (http://fernandotapiarico.com/)
MÃ³vil: +34 654 388 389 (tel:%2B34%20654%20388%20389)
Email: ***@gmail.com (mailto:***@gmail.com)
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric

Erik Elmore

2012-01-18 10:09:51 UTC

Permalink

All of those functions are the domain of xmpp server software. I don't
know of any xmpp protocols that allow clients to do all of these things and
certainly not any that allow non-admin users to modify server-stored data
for other users. What are you trying to accomplish, exactly? I'm a little
confused because your message seems to contradict itself.

+=
Erik Elmore

Post by Fernando Tapia Rico
Hi all,
I just started using xmpp4r, so it could be a newbie question. I wonder if
there is a way to handle users, their rosters and their info. All of these
- Create/Register an user (I found jabber:iq:register)
- Delete an user
- Update user information (I saw xmpp4r can update user information, but
it should be done from the current user's account, not from admin)
- Add a user to another user's roster
- Delete a user from another user's roster
I saw Openfire Browser administration let me do this, but I'm not sure if
it's an internal API or part of the XMPP protocol.
Thanks in advance
Cheers
--
Fernando Tapia Rico
http://fernandotapiarico.com
Móvil: +34 654 388 389
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel

Fernando Tapia Rico

2012-01-18 10:23:09 UTC

Permalink

Hi Erik,
all of the server-stored data is going to be manage from an administration account, that's for sure.
I want to be able, from an admin account, to add users, delete users and modify their information and contacts. The point here is that I have a web app (with a other services running, search service, recommendation service and more) who needs to manage users, register the relationships between users, and the "friendship" requests. So:

- if a user creates a new user on the web, a new user must be created on the jabber server (I saw that with an IQ query jabber:iq:register this can be done).
- if the user wants to delete his account, in addition to remove his data on the web database an other services, his account must be removed in the jabber server.
- if the user request a "friendship" to the web API, this relationship must be updated in all the services and in the jabber server. Same, when an user accepts the "friendship" request.
- if the user wants to remove a contact, that action must be reflected on all the services, including the chat service (jabber)
- and the last one, if a user updates his information, the jabber service must reflect this changes.

So, I wonder if there is a way of doing all this stuff using the admin account. Sorry for not being so specific in the first mail, hope this clears the situation a little bit. Thanks for your help
Regards,

--
Fernando Tapia Rico
http://fernandotapiarico.com (http://fernandotapiarico.com/)
MÃ³vil: +34 654 388 389 (tel:%2B34%20654%20388%20389)
Email: ***@gmail.com (mailto:***@gmail.com)
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric

All of those functions are the domain of xmpp server software. I don't know of any xmpp protocols that allow clients to do all of these things and certainly not any that allow non-admin users to modify server-stored data for other users. What are you trying to accomplish, exactly? I'm a little confused because your message seems to contradict itself.
+=
Erik Elmore

Post by Fernando Tapia Rico
Hi all,
- Create/Register an user (I found jabber:iq:register)
- Delete an user
- Update user information (I saw xmpp4r can update user information, but it should be done from the current user's account, not from admin)
- Add a user to another user's roster
- Delete a user from another user's roster
I saw Openfire Browser administration let me do this, but I'm not sure if it's an internal API or part of the XMPP protocol.
Thanks in advance
Cheers
--
Fernando Tapia Rico
http://fernandotapiarico.com (http://fernandotapiarico.com/)
MÃ³vil: +34 654 388 389 (tel:%2B34%20654%20388%20389)
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel

_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel

Erik Elmore

2012-01-18 10:41:21 UTC

Permalink

When you say "using the admin account", do you mean that the application
does this via XMPP protocol, which is logged in as an xmpp client session
which happens to have admin privileges on the xmpp server? If this is the
case, I don't know of any xmpp protocol for managing other users.

I would propose an alternative, however. If your users use your website to
access these services, then why not just implement these functions as a
BOSH client under the users' own identities? This way, your users log into
your service using their own account and can therefore manage their own
rosters via XMPP. This could work well even if you require that your users
sometimes use normal xmpp clients because the app will act as their own
xmpp identity when dealing with the server.

+=
Erik Elmore

Post by Fernando Tapia Rico
Hi Erik,
all of the server-stored data is going to be manage from an administration
account, that's for sure.
I want to be able, from an admin account, to add users, delete users and
modify their information and contacts. The point here is that I have a web
app (with a other services running, search service, recommendation service
and more) who needs to manage users, register the relationships between
- if a user creates a new user on the web, a new user must be created on
the jabber server (I saw that with an IQ query jabber:iq:register this can
be done).
- if the user wants to delete his account, in addition to remove his data
on the web database an other services, his account must be removed in the
jabber server.
- if the user request a "friendship" to the web API, this relationship
must be updated in all the services and in the jabber server. Same, when an
user accepts the "friendship" request.
- if the user wants to remove a contact, that action must be reflected on
all the services, including the chat service (jabber)
- and the last one, if a user updates his information, the jabber service
must reflect this changes.
So, I wonder if there is a way of doing all this stuff using the admin
account. Sorry for not being so specific in the first mail, hope this
clears the situation a little bit. Thanks for your help
Regards,
--
Fernando Tapia Rico
http://fernandotapiarico.com
Móvil: +34 654 388 389
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric
All of those functions are the domain of xmpp server software. I don't
know of any xmpp protocols that allow clients to do all of these things and
certainly not any that allow non-admin users to modify server-stored data
for other users. What are you trying to accomplish, exactly? I'm a little
confused because your message seems to contradict itself.
+=
Erik Elmore
Hi all,
I just started using xmpp4r, so it could be a newbie question. I wonder if
there is a way to handle users, their rosters and their info. All of these
- Create/Register an user (I found jabber:iq:register)
- Delete an user
- Update user information (I saw xmpp4r can update user information, but
it should be done from the current user's account, not from admin)
- Add a user to another user's roster
- Delete a user from another user's roster
I saw Openfire Browser administration let me do this, but I'm not sure if
it's an internal API or part of the XMPP protocol.
Thanks in advance
Cheers
--
Fernando Tapia Rico
http://fernandotapiarico.com
Móvil: +34 654 388 389
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel

Fernando Tapia Rico

2012-01-18 10:58:00 UTC

Permalink

Yeah, when I said "admin account", I meant an account which have admin privileges on the jabber server and it's connected using an XMPP client and communicates with the server using XMPP protocol.

I just wanna check if that was possible. I saw some extensions like XEP-0133 that could be helpful, but it seems that not all the jabber servers implement them.

Thanks for your help. I'll try with the BOSH thingy.
Cheers

--
Fernando Tapia Rico
http://fernandotapiarico.com (http://fernandotapiarico.com/)
MÃ³vil: +34 654 388 389 (tel:%2B34%20654%20388%20389)
Email: ***@gmail.com (mailto:***@gmail.com)
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric

When you say "using the admin account", do you mean that the application does this via XMPP protocol, which is logged in as an xmpp client session which happens to have admin privileges on the xmpp server? If this is the case, I don't know of any xmpp protocol for managing other users.
I would propose an alternative, however. If your users use your website to access these services, then why not just implement these functions as a BOSH client under the users' own identities? This way, your users log into your service using their own account and can therefore manage their own rosters via XMPP. This could work well even if you require that your users sometimes use normal xmpp clients because the app will act as their own xmpp identity when dealing with the server.
+=
Erik Elmore

Post by Fernando Tapia Rico
Hi Erik,
all of the server-stored data is going to be manage from an administration account, that's for sure.
- if a user creates a new user on the web, a new user must be created on the jabber server (I saw that with an IQ query jabber:iq:register this can be done).
- if the user wants to delete his account, in addition to remove his data on the web database an other services, his account must be removed in the jabber server.
- if the user request a "friendship" to the web API, this relationship must be updated in all the services and in the jabber server. Same, when an user accepts the "friendship" request.
- if the user wants to remove a contact, that action must be reflected on all the services, including the chat service (jabber)
- and the last one, if a user updates his information, the jabber service must reflect this changes.
So, I wonder if there is a way of doing all this stuff using the admin account. Sorry for not being so specific in the first mail, hope this clears the situation a little bit. Thanks for your help
Regards,
--
Fernando Tapia Rico
http://fernandotapiarico.com (http://fernandotapiarico.com/)
MÃ³vil: +34 654 388 389 (tel:%2B34%20654%20388%20389)
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric

All of those functions are the domain of xmpp server software. I don't know of any xmpp protocols that allow clients to do all of these things and certainly not any that allow non-admin users to modify server-stored data for other users. What are you trying to accomplish, exactly? I'm a little confused because your message seems to contradict itself.
+=
Erik Elmore

_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel

Erik Elmore

2012-01-18 11:11:11 UTC

Permalink

XEP 133 doesn't allow you to change anyone's roster.

+=
Erik Elmore

Post by Fernando Tapia Rico
Yeah, when I said "admin account", I meant an account which have admin
privileges on the jabber server and it's connected using an XMPP client and
communicates with the server using XMPP protocol.
I just wanna check if that was possible. I saw some extensions like
XEP-0133 that could be helpful, but it seems that not all the jabber
servers implement them.
Thanks for your help. I'll try with the BOSH thingy.
Cheers
--
Fernando Tapia Rico
http://fernandotapiarico.com
Móvil: +34 654 388 389
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric
When you say "using the admin account", do you mean that the application
does this via XMPP protocol, which is logged in as an xmpp client session
which happens to have admin privileges on the xmpp server? If this is the
case, I don't know of any xmpp protocol for managing other users.
I would propose an alternative, however. If your users use your website to
access these services, then why not just implement these functions as a
BOSH client under the users' own identities? This way, your users log into
your service using their own account and can therefore manage their own
rosters via XMPP. This could work well even if you require that your users
sometimes use normal xmpp clients because the app will act as their own
xmpp identity when dealing with the server.
+=
Erik Elmore
Hi Erik,
all of the server-stored data is going to be manage from an administration
account, that's for sure.
I want to be able, from an admin account, to add users, delete users and
modify their information and contacts. The point here is that I have a web
app (with a other services running, search service, recommendation service
and more) who needs to manage users, register the relationships between
- if a user creates a new user on the web, a new user must be created on
the jabber server (I saw that with an IQ query jabber:iq:register this can
be done).
- if the user wants to delete his account, in addition to remove his data
on the web database an other services, his account must be removed in the
jabber server.
- if the user request a "friendship" to the web API, this relationship
must be updated in all the services and in the jabber server. Same, when an
user accepts the "friendship" request.
- if the user wants to remove a contact, that action must be reflected on
all the services, including the chat service (jabber)
- and the last one, if a user updates his information, the jabber service
must reflect this changes.
So, I wonder if there is a way of doing all this stuff using the admin
account. Sorry for not being so specific in the first mail, hope this
clears the situation a little bit. Thanks for your help
Regards,
--
Fernando Tapia Rico
http://fernandotapiarico.com
Móvil: +34 654 388 389
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric
All of those functions are the domain of xmpp server software. I don't
know of any xmpp protocols that allow clients to do all of these things and
certainly not any that allow non-admin users to modify server-stored data
for other users. What are you trying to accomplish, exactly? I'm a little
confused because your message seems to contradict itself.
+=
Erik Elmore
Hi all,
I just started using xmpp4r, so it could be a newbie question. I wonder if
there is a way to handle users, their rosters and their info. All of these
- Create/Register an user (I found jabber:iq:register)
- Delete an user
- Update user information (I saw xmpp4r can update user information, but
it should be done from the current user's account, not from admin)
- Add a user to another user's roster
- Delete a user from another user's roster
I saw Openfire Browser administration let me do this, but I'm not sure if
it's an internal API or part of the XMPP protocol.
Thanks in advance
Cheers
--
Fernando Tapia Rico
http://fernandotapiarico.com
Móvil: +34 654 388 389
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel

Fernando Tapia Rico

2012-01-18 11:17:38 UTC

Permalink

Yeah, I know, but at least it was an option for deleting users. But well, if it's not wide implemented, then it's not really interesting.
Cheers

--
Fernando Tapia Rico
http://fernandotapiarico.com (http://fernandotapiarico.com/)
MÃ³vil: +34 654 388 389 (tel:%2B34%20654%20388%20389)
Email: ***@gmail.com (mailto:***@gmail.com)
Twitter | GitHub | Skype: fertapric
LinkedIn: http://www.linkedin.com/in/fertapric

Post by Erik Elmore
XEP 133 doesn't allow you to change anyone's roster.
+=
Erik Elmore

When you say "using the admin account", do you mean that the application does this via XMPP protocol, which is logged in as an xmpp client session which happens to have admin privileges on the xmpp server? If this is the case, I don't know of any xmpp protocol for managing other users.
I would propose an alternative, however. If your users use your website to access these services, then why not just implement these functions as a BOSH client under the users' own identities? This way, your users log into your service using their own account and can therefore manage their own rosters via XMPP. This could work well even if you require that your users sometimes use normal xmpp clients because the app will act as their own xmpp identity when dealing with the server.
+=
Erik Elmore

All of those functions are the domain of xmpp server software. I don't know of any xmpp protocols that allow clients to do all of these things and certainly not any that allow non-admin users to modify server-stored data for other users. What are you trying to accomplish, exactly? I'm a little confused because your message seems to contradict itself.
+=
Erik Elmore

_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel