# User API keys should use OAEP padding

**URL:** <https://meta.discourse.org/t/user-api-keys-should-use-oaep-padding/354056>\
**Category:** Feature\
**Tags:** user-api\
**Created:** [June 1, 2024, 7:00am UTC](https://meta.discourse.org/t/user-api-keys-should-use-oaep-padding/354056 "2024-06-01T07:00:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mqmenchaca](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@mqmenchaca](https://meta.discourse.org/u/mqmenchaca)\
**Post date:** [February 14, 2025, 10:31pm UTC](https://meta.discourse.org/t/user-api-keys-should-use-oaep-padding/354056/2 "2025-02-14T22:31:14Z")

</div>

@simon Yes this is definitely causing problems with Node v22. It would be great to not revert security patches. It would be nice to set a flag in the API call or site setting in Discourse to choose the desired padding. (That way people can keep the existing default if they would like.)

---

_[View the full topic](https://meta.discourse.org/t/user-api-keys-should-use-oaep-padding/354056)._