Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Ability to respond with custom response code from Authentication class

  • Filter
  • Time
  • Show
Clear All
new posts

  • Ability to respond with custom response code from Authentication class


    Use case: We are developing a custom authentication class that extends:
    This class will retrieve the Bearer token from Auth header and will verify it as jwt token using issuer and audience. When coding this I didn't see a way to configure a different response code for failed scenarios other than 401. We need it to be 403 in some cases.

    I pulled latest code from mirth github just a day before 3.12.0 was released and verified that in fact 401 is hard coded.

    For this purpose I have created this ticket on github:

    A work around solution might be to address this using filter code but it is not elegant and not ideal.

    Question is this, have anyone else had such a use case as us and if so how did you solve it?