This would be a good answer for me except that I cannot get header based auth to work so I am attempting to do it with forms and am also getting CSRF. Any solution? I am trying to create a new topic using the API.
We will need more information to be able to help. Can you share a code snippet showing how you are trying to use the header based authentication?
1 „Gefällt mir“
The problem I’ve been having stems mostly from whenever I try to make a call with header based auth, the accepted headers are always “User-Api-Key” and “User-Client-Id” instead of “Api-Key” and “Api-Username” so I get CORS errors. I do not believe I need user based keys. I am just trying to do a simple authenticated request to create a new topic. If I try to use the “User-Api-Key” I am getting a 403 errors.
This is sample code (Angular Typescript), but should be similar to other setups:
createNewTopic(postBody: any) {
let url = "myserver.com/posts.json";
let CATEGORY_ARTICLES = 6;
let topicContent = `
<p>Some content
</p>
<p>Did that work?</p>
`;
let post = {
"title": "Tdk Test 1",
"raw": topicContent,
"category": CATEGORY_ARTICLES,
"target_usernames": "tdekoekkoek",
"archetype": "",
"created_at": new Date()
}
let headers = new HttpHeaders()
.set("Accept", "application/json")
.set("User-Api-Key", DISCOURSE_API_KEY)
.set("User-Key", "system")
.set("Content-Type", "application/x-www-form-urlencoded")
let options = {headers: headers};
return this.http.post(url, post, options);
}
user-api-key and user-client-id are a completely different method of authentication. Regular API keys won’t work with those headers. What happens when you use the correct header names? (api-key and api-username)
1 „Gefällt mir“
I get a CORS error because the server is expecting User-Api-Key. I examine the expected headers in the OPTIONS response and that is what it says. There is a similar topic elsewhere on this forum where a user was experiencing this when calling from a javascript app.
Oh, so you are trying to make this request from a client-side javascript application? That is not permitted for numerous reasons. For example, if you include an admin API key in the source code of your javascript app, any user could gain full admin access to your forum. Here is a previous topic on the subject.
2 „Gefällt mir“
Yes that is what I am trying to do. That should be more clearly documented. That has been my whole strategy since getting started with Discourse. I appreciate your help. Been battling with this for days and reading the documentation. Will have to rethink my whole approach as I am currently building a serverless application though I do have access to a node.js server.
1 „Gefällt mir“
This isn’t a restriction specific to Discourse - in general it is a bad idea to include admin credentials in the source code of a website.
If you can make the Discourse API call from your node.js server, that would probably be the best solution. If you need your application to be purely client-side, then requesting user-specific api keys is an option, although their setup is a lot more complex: User API keys specification
2 „Gefällt mir“
Frankly accessing APIs from client applications with CORS enabled is extremely common and standard. I can’t believe there is not a more secure way of doing this. An entire industry revolves around hosted APIs that are accessed from different domains. As for accessing with user api, I’ve seen how to create those, but am unclear about what the actual credentials are. I am always getting 403 permission denied when using that method.
1 „Gefällt mir“
Ich glaube, ich befinde mich in einer ähnlichen Situation.
Ein paar Worte zum Anwendungsfall:
Ich nutze Discourse als Backend und baue das Frontend in VueJS. Ich beabsichtige, ausschließlich die REST-API zu verwenden. Für jeden Benutzer auf unserer Plattform habe ich einen eigenen API-Schlüssel erstellt und verwende sowohl die Header (Api-Key & Api-Username) zur Authentifizierung.
Jeder Benutzer authentifiziert sich sicher bei unseren Servern und erhält daraufhin sein Discourse-Token zur Authentifizierung. Anschließend möchten wir dieses Token (in einem VueJS-Frontend) verwenden, um API-Anfragen zu senden (Themen erstellen, Beiträge verfassen, bearbeiten usw.).
Nichts ist hart kodiert; alle Tokens werden nach einer ordnungsgemäßen Authentifizierung empfangen.
Das Problem:
Ich erhalte eine CORS-Fehlermeldung, obwohl ich sie in der app.yml aktiviert und im Abschnitt „Sicherheit
@david kann Discourse nicht einfach ein Sitzungsgeheimnis mit einem HMAC signieren lassen, und dieses Sitzungsgeheimnis kann wiederum verwendet werden, um Dinge in der gegebenen Sitzung zu signieren? Wenn es gestohlen wird, dann würden vermutlich die Sitzungs-Cookie oder der CSRF-Nonce auch nicht gestohlen werden. Es ist ein bisschen wie eine Zertifikatskette – man muss den Root-Schlüssel nicht im Browser hinterlegen.
Diese sind nur für die Admin-API. So wie ich es verstanden habe, müssen Sie für JavaScript-Clients, wie oben erwähnt, User API keys specification prüfen.