This week we released Confluence 11 rc1. There are changes in this release that may directly affect third-party apps.
New in 11.0
To find out what’s in this release, check out the Confluence 11.0 beta release notes.
Get started
Download the beta from our site to start testing your app for compatibility with the changes. Be sure to take a look at our Preparing for Confluence 11.0 guide to find out what you need to do to make your app compatible. We’ll update that page regularly, so keep an eye on it to see any changes.
Reminder: for future release updates, make sure you visit the Atlassian changelog, and consider subscribing to the RSS feed.
The Atlassian Confluence team
I tested with three of our macros on Confluence page.
I can reproduce the following problem:
The response to the request to our apps REST controller is as follows:
message: "Rate limit exceeded."
I didn’t make changes to the rate limiting configuration. But it seems the default configuration might be too strict. I don’t know how rate limiting exactly works and if its configured per endpoint or in general. But as said. Having the same macro on a page multiple times is not unusual and the default rate limiting should yet appy in my opinion.
Very much looking forward to your response!
Best,
Cedric
We are using “com.atlassian.confluence.user.UserVerificationTokenManager” inside one of our Confluence DC apps (such as user password resets and secure verification workflows). Now it seems UserVerificationTokenManager is hidden from the OSGI.
Could you please reconsider exposing a public, supported interface for UserVerificationTokenManager (or providing an equivalent public service component) to the OSGi container in Confluence Data Center?
Alternatively, if token management has been intentionally moved behind a new public API layer or service in Confluence 11.0, could you point us toward the correct public documentation or service interface we should be using instead?
Hi Cederic! Yes, in 11.0 rate limiting is enabled by default. You can find more details about it here: Improving instance stability with rate limiting | Confluence Data Center 10.2 | Atlassian Documentation - What kind of traffic are you seeing? What endpoints are being limited? We added the ability to rate limit individual endpoints for plugin vendors, however the global configuration mentioned above is most likely your cause, as the effective limit is the lower of the two configurations.
The endpoints being limited were the ones from our plugin.
However, today, I can’t seem to reproduce the issue.
Very strange. I’ll get back to you if I can reproduce the issue some point.
Best,
Cedric
Is the rate limiting going to be disabled when performing the scale and performance tests in the future with Confluence 11?
