No se puede actualizar el correo electrónico mediante API: error invalid_access

Desarrollador
1

Hi Guys,

Im getting an error when trying to use the API to update email.
I have looked at the logs and can see the following:

Started PUT “/discussion/users/davetest/preferences/email.json” for xx.xx.xx.xx at 2018-05-11 12:22:11 +0000

Processing by UsersEmailController#update as JSON

Parameters: {“api_key”=>;"[FILTERED]", “api_username”=>;“daveAdmin”, “email”=>;“[new.email@example.com](mailto:new.email@example.com)”, “username”=>;“davetest”}

Can’t verify CSRF token authenticity.

This is a PUT request, but looking at the scopes below, doesnt seem like PUT is supported for the WRITE scope? surely im misunderstanding, so could someone please assist?

I have re-generated the all-user api-key, also created specific user api-keys to use, but same result.

SCOPES = {
read: [:get],
write: [:get, :post, :patch],
message_bus: [[:post, ‘message_bus’]],
push: nil,
notifications: [[:post, ‘message_bus’], [:get, ‘notifications#index’], [:put, ‘notifications#mark_read’]],
session_info: [[:get, ‘session#current’], [:get, ‘users#topic_tracking_state’]]
}
2

Can you verify the content-type that you are making the API request as? It needs to be

"Content-Type: multipart/form-data;"

If it is not that content type you may see the CSRF token error.

1 me gusta
3

Hi, thanks for the reply.
I actually had tried it both with ‘application/json’ and ‘application/x-www-form-urlencoded’ and neither worked. I have now tried it with what you suggested (via postman) and getting:

“You are not permitted to view the requested resource. The API username or key is invalid.”

I have regenerated the global api key that is used for “all users” and using it with my own username, which is an admin too…

shahid

4

Here is an example of my postman request maybe you can spot any differences with what you are doing? I’m also using the “all users” key with an admin username.

image
image.png1036×550 45.7 KB

2 Me gusta
5

yes, its the same, im using the Postman API collection supplied by discourse. So using it as suggested. I will try again tonight and see if i get any different results. Will update when ive tried. Thanks for assisting, much appreciated. Do let me know if you have any other idea.

1 me gusta
6

I’m experiencing this issue too and I’m wondering if it has anything to do with using an oauth provider for signing in and so this specific page is being blocked?

7

It most likely isn’t the oauth provider because the api keys will bypass it.

Could you share the code for your API request?

8

in python:

import json
import requests
import time

my_token = ''

url_base = '<>'
update_email = url_base + "users/<my_username>/preferences/email.json"

headers = {
    "Content-Type": "multipart/form-data",
    'user-agent': 'my-app/0.0.1',
    'Api-Key': my_token,
    'Api-Username': '<my_username>'
}

data = {
  "email": "<new_email>"
}

response = requests.put(update_email, data=data, headers=headers)

print(response.text)

Edit: very similar code for setting groups on users etc worked, so the key / username combo (which is a user with admin privileges) works.

Edit 2: I’m guessing from other browsing in the forum that this has to be done directly in the database, (or rather, via the console) which is impossible for us.

9

Any more thoughts on this? My feeling is that someone with admin access rights should be able to set the e-mail of a person.

10

How so? I don’t think this is possible with the existing web UI, which defines the API. Therefore it can’t be done.

1 me gusta
11

You mean that the UX/API should make it possible to set a user’s email address to whatever you want. (Not that you believe that it is currently possible.)

You can initiate a change (via UX and I presume API) by editing their profile and entering the new address, but it won’t be changed until they click the link in their email. Is that good enough? If not, you’ll need to do it from the console or a plugin.

1 me gusta
12

Exactly.

Whenever I enter something in the UX for editing the e-mail (which I can only access through the direct URL i.e. https://<discourse>/u/<username>/preferences/email, there is no link through the user’s profile) it pops up that I can’t do this after clicking on “Change”:

image

And this is on my own account as an admin. I don’t get an e-mail.

13

También he llegado a este punto…

@pfaffman: mencionaste que es posible cambiar la dirección de correo electrónico en el perfil, pero eso requiere que email editable esté activado, ¿verdad?

He aprendido que no hay forma de que un administrador o una llamada a la API administrativa inicie un cambio de dirección de correo electrónico a menos que también se permita a los usuarios cambiar sus propias direcciones, ¿es así? Puedo perfectamente aceptar que se envíe un correo de confirmación y que el cambio deba ser autorizado por el usuario.

Mi caso de uso es que los usuarios se gestionarán desde otra aplicación a través de la API. Por lo tanto, no quiero que puedan cambiar sus direcciones de correo electrónico por sí mismos solo en Discourse.

14

¿Podrías implementar Inicio de sesión único y convertir tu otra aplicación en la fuente de inicios de sesión?

Existe una configuración específica de SSO llamada sso overrides email que hace exactamente lo que intentas lograr. Si tienes SSO configurado, puedes usar el endpoint sync_sso y pasar la nueva dirección de correo electrónico.

3 Me gusta
15

¡Gracias @blake, eso es un desafío pero divertido :wink:

Tendría que importar las contraseñas de Discourse al centro de identidad… oh, Dios mío.

Ayudé a mi escenario original con un proceso de tres pasos: habilitar la edición del correo electrónico, iniciar el cambio de dirección de correo electrónico y deshabilitar la edición del correo electrónico. Lo cual parece un poco excesivo, pero funciona.

Pensaré en el escenario de SSO.

1 me gusta