ContributionsMost RecentMost LikesSolutionsSoapUI stores access token with project XML? Hi, I've externalized properties that are used for e.g. authentication to a properties file that a user must load into SoapUI and fill out the credentials. The configured OAuth2 profile then uses these properties to get an access token. The idea is that the properties should not be stored with the project XML file as this should be shared with others. Now I've noticed that while the credentials are not stored, the access token is. Though it expires in 2 hours, it's still not a good solution to store this token as part of the project XML file. Is there some way / option to avoid this? Ordering of Resources and Requests Hi, I've noticed that autmatically sorting projects and services alphabetically is possible, this works fine. However, there is also the option to sort requests alphabetically, and this does not seem to work: Or does this option mean some other kind of request? Also, it puzzles me that it's still not possible to change the order of resources and request by dragging the item in the list (at least it's not working for me). This is a really weird decision, as now resources or requests that are added later just gets added to the end, which makes it difficult to group similar resources and requests. The basic tree component seems to support re-ordering, however, it's disabled.