![]() ![]() 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. For a small number of projects (less or equal to 100) with 1,000 to 5,000 issues in total and about 100-200 users, a recent server (multicore CPU) with 8GB of available RAM and a reasonably fast hard drive (7200 rpm or faster) should cater for your needs.Please also read the information below regarding server and client software and hardware requirements for Jira. Please read the Supported platforms page for Jira applications, which lists the required server and client software supported by Jira applications for: If you're upgrading to Jira 9.7 be sure to review the latest release and upgrade notes here. As such, Jira must be able to communicate and authenticate with itself. Jira is a 'web application', meaning it runs centrally on a server, and users interact with it through web browsers from any computer on the same network. Jira applications installation requirements Choose from a set of supported apps to install.Option to migrate to your own server later.No installation required, get started in 5 minutes.If the session should be invalidated after succeeded authentication using personal access token.No hardware? No problem! Try using Jira applications in the Cloud. How many days before sending an e-mail notification about tokens that will expire soon. The CRON expression for the scheduler job that sends notifications about expired tokens and about tokens that will expire soon. The maximum number of items allowed in the Authentication Cache. The length of time, in minutes, an item can stay in the Authentication Cache before being removed. Maximum number of tokens allowed per user. If you decided to change this property, the new value will apply only to tokens created after your change and won't affect already created tokens. ![]() ![]() Maximum number of days for a token to expire. The delay before expired tokens are removed from the database, in days. The cron expression must be surrounded by single-quotes. The CRON expression for the expired token pruning scheduler job. '0 0 0 * * ?' - 12 am local time, every day The interval at which the scheduler job is updating the 'last accessed at' property of each token, in minutes. Whether mail notifications are globally enabled. If users should be able to create tokens that do not expire. Whether personal access tokens are globally enabled. Limit token creationĪdministrators can use system properties to limit the number of tokens people can create, and set expiry rules. Your token is now revoked and can't be used for further authentication. Select Revoke next to the token you want to delete.In Confluence, select your profile picture at the top right of the screen, then choose Settings > Personal access tokens.In Jira select your profile picture at the top right of the screen, then choose Personal Access Tokens.If for any reason, for instance, a security breach, you need to revoke your token, you can do it quickly from your Atlassian application: If attempting to use the PAT on a script or with some other method, you should still follow the Bearer Token OAuth standard. ![]() The "Bearer" part should not be changed, nor should you need to inform which user is making the request.
0 Comments
Leave a Reply. |