In this case, you may need to configure it to supply the authorization header, as described above, rather than relying on its default mechanism. This means that it may not behave as expected. For example you can specify the -u argument with curl as followsĢ curl -D-X GET -H "Authorization: Basic ZnJlZDpmcmVk" -H "Content-Type: application/json" " Advanced topics Authentication challengesīecause JIRA permits a default level of access to anonymous users, it does not supply a typical authentication challenge. Some HTTP client software expect to receive an authentication challenge before they will send an authorization header. Most client software provides a simple mechanism for supplying a user name and password and will build the required authentication headers automatically. On this page we will show you a simple example of basic authentication. Any authentication that works against JIRA will work against the REST API. In most cases, the first step in using the JIRA REST API is to authenticate a user account with your JIRA site. Furthermore, if you log in and do not have permission to view something in JIRA, you will not be able to view it using the JIRA REST API either. This means that if you do not log in, you are accessing JIRA anonymously. ![]() JIRA's REST API is protected by the same restrictions which are provided via JIRAs standard web interface. This is one of three methods that you can use for authentication against the JIRA REST API the other two being cookie-based authentication and OAuth (see related information). Our support site has approximately: 285,000 issues, 2,500,000 comments, 75 custom fields, and 22 projects.įor more information, you can also refer to Scaling Jira.This page shows you how to allow REST clients to authenticate themselves using basic authentication (user name and password). Our public site has approximately: 145,000 issues, 255,000 comments, 120 custom fields, and 115 projects. This server runs Apache, various monitoring systems, and two Jira application instances: If your system will experience a large number of concurrent requests, running Jira applications on a multicore CPU machine will increase the concurrency of processing the requests, and therefore, speed up the response time for your users.įor reference, we have a server that has a 2 Intel(R) Xeon(R) CPU E5520 2.27GHz (16 logical cores) with 32GB of RAM. This is because each created project can create new workflows, new custom fields, new permissions schemes, new screens, etc. If you’re manually installing/upgrading Jira on a 32-bit system by using the archive, you need to decrease the maximum heap size available to Jira. See the upgrade notes for more information.įor 100 projects or more you should monitor Jira memory usage and allocate more memory if required. However, if you're using a 32-bit operating system, you shouldn't allocate more than 1GB of RAM to Jira.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |