Gadgets and Dashboards 2.0 : Allowing Other Applications to Access Data on Your Behalf
This page last changed on Nov 18, 2009 by ggaskell.
This page tells you how to access the data and resources on an Atlassian application from another application via OAuth. On this page: Allowing a Consumer Application to Access the Resources of an Atlassian Servicer ProviderThe following procedure uses an Atlassian gadget to demonstrate how an application (the consumer) can access the resources of your Atlassian application via OAuth, on your behalf. For the consumer application to gain access to your Atlassian application's resources, you must have a user account with your Atlassian application. To allow a consumer application to access your Atlassian application's resources via a gadget,
Screenshot: Approving a Gadget's Access to your Resources Screenshot: Request for Access Message Screenshot: A Gadget after OAuth Access has been Approved Revoking Access TokensOnce you have allowed a consumer application to access an Atlassian service provider's resources on your behalf, the access token issued to the consumer will be accessible from your account area of the Atlassian service provider application. This area shows all access tokens issued by the service provider to all consumer applications, to whom you have granted access to your service provider's resources. You can revoke any access token from this area. Doing this prevents the applicable consumer application from accessing the service provider's resources on your behalf until you grant that consumer access again. To revoke an access token,
Screenshot: OAuth Access Tokens page |
![]() |
Document generated by Confluence on Nov 22, 2009 17:46 |