JWT Migration FAQ

Introduction

Since Version 30.97 D, Momentus has supported two authorization methods for the API/SDK: Momentus Authorization and JSON Web Token (JWT). Moving forward, we will begin sunsetting support for Momentus Authorization (aka "basic auth") in favor of JWT. 

Please be aware that support for "Momentus Authorization" for the API will end in 2025.

Frequently Asked Questions (FAQ)

What do I gain from moving to JWT?

• The new changes include numerous benefits for you. Please see this article's "Why make this change" section to highlight just a few of those benefits.

Why JWT and not something else?

• JWT is the strongest choice for authentication in which both sides are trusted. In this scenario, your client applications are using an API to communicate with your Momentus installation. In this case, generating a JWT is the fastest and most secure option.

What about solutions that Momentus created for me?

• All solutions that are covered by an Annual Managed Services subscription will be upgraded in a timely manner. If you are unsure if you have a Managed Services subscription for your integrations, please connect with your primary Momentus contact.

Do I need Momentus to do this work, or am I responsible for it?

• You are responsible for migrating your implementations, though we are here to help.

Will I get alerted if I have an application that I haven't migrated yet or missed?

• We will be on the lookout for any detected use of basic authentication and make an effort to proactively notify clients as we approach any deadlines but there is always a chance that we may not identify a specific use case or integration pattern. Therefore, it is highly recommended that you work with your primary Momentus contact before upgrading if you have any concerns.

How do I generate a JWT for my solution written in Python, PHP, Perl, Java, and so on?

• jwt.io has an extensive list of common libraries used in various languages. See JSON Web Token Libraries on jwt.io for more information. We have also documented key information for manually generating a token with an appropriate payload and signature in JWT Authentication and the Refreshed SDK Overview—Momentus Support Center.

Can I migrate slowly or is it all or nothing?

• We recommend starting in your test environment to catch any fringe cases. This also allows a slow rollout as you progress migration.

What happens if I don't migrate to JWT and we upgrade to the next version?

• Your custom integration will not be able to authenticate and thus will not function. Please contact us if you have concerns or issues with the migration.

Can we roll back if we missed something?

• While it is something we are considering, there is no easy option to roll back for missed integrations at this time. If you have any concerns, it is highly recommended that you work with your primary Momentus contact prior to upgrading.

Can we migrate our test environment first?

• Absolutely, and that is the preferred method. It provides a live environment to resolve any issues before migrating your production environment.

I have other questions not answered here. How do I get help?

• Please do not hesitate to reach out to our client care team and/or your primary Momentus contact with any further questions, concerns, or issues.

References

• Upgrade Considerations – Momentus Support Center
• JWT Authentication and the Refreshed SDK Overview – Momentus Support Center