Anonymous Access to Remote API
Configuring Confluence Security
- Confluence Security Overview and Advisories
- Proxy and HTTPS setup for Confluence
- Configuring Secure Administrator Sessions
- Confluence Cookies
- Using Fail2Ban to limit login attempts
- Securing Confluence with Apache
- Best Practices for Configuring Confluence Security
- Encrypting passwords in server.xml
- Hiding the People Directory
- Configuring Captcha for spam prevention
- Hiding external links from search engines
- Configuring Captcha for failed logins
- Configuring XSRF Protection
- User Email Visibility
- Anonymous Access to Remote API
- Configuring RSS Feeds
- Preventing and Cleaning Up Spam
On this page
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications
XML-RPC and SOAP remote APIs were deprecated in Confluence 5.5 and are disabled by default. They can be enabled, but we recommend using the fully supported Confluence Server REST API wherever possible.
Administrators may wish to disable anonymous access to the Confluence remote API (XML-RPC and SOAP APIs) to make it harder for malicious users to write 'bots' that perform bulk changes to the site.
To disable anonymous access to the remote API:
- Select Administration menu , then select General Configuration
- Select Security Configuration in the left-hand panel. The Security Configuration screen will appear.
- Select Edit.
- Clear the Anonymous Access to Remote API checkbox.
- Select Save.
Notes
This page is about access to the remote API. If you are looking for information about preventing anonymous users from accessing Confluence, see Global Permissions Overview.
Last modified on Dec 10, 2024
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications
Powered by Confluence and Scroll Viewport.