ADT access to ABAP Trial

[p215636]

Hello,

I experiencing a technical issue with accessing ABAP Trial within BTP.

When I try to access the ABAP Cloud instance from within ADT by clicking on logon to Project

SAP Service screen is presented and SAML authentication seems to work

However the departure from the usual screens is that I’m then presented with the following sign-in dialog

BTP Cockpit access works and in the past I've used to approach to over ride any caching issues..

The Browser was re-started to ensure no caching issues.

Regards

[ajay_110125]

I am experiencing the same issue. It's asking ID & password which I don't know where should I get from

[p215636]

Ajay,

Thank you for taking the time to confirm you are experiencing the same issue, greatly appreciated.

Hopefully we will get a response from SAP soon…

[p215636]

To those who might be experiencing the issue can I kindly request you pen a quick post to confirm you are also experiencing the issue. This issue might be limited to a subset of users and not affecting all trial users, it will assist SAP in resolving the issue faster!

[GerUser1234]

I have exactly the same Problem with the login.

[sratz]

Could you try to delete the ADT project and to re-create it using the current URL of the ABAP trial instance?

Background: In case of expiration of the trial account and re-registration the user could have been provisioned on a different ABAP instance with a different endpoint URL and the existing ADT project may not work anymore.

Related: https://community.sap.com/t5/application-development-discussions/authorization-required-access-to-lo...

[SachinArtani]

Exactly the issue. When the trial account expires, we get to ask the username and password. We need to create a new trial account if this happens.

[p215636]

Hello,

Thank you for taking the time to look at my issue and apologies for the delay in getting back to you.

I did try your suggestion of deleting the ABAP Cloud Project,

but without any success, once I entered the ABAP Service Instance URL to create another ABAP Cloud Project, the error raised it's ugly face again.

So you got me thinking was this something to do with the containerisation of objects and why I had not experienced this issue in the past and why this issue was limited to a small sample set of users.

In the past we had to manually delete our Trial Accounts at the Account Explorer level, in essence wiping the entire slate clean. 

Lately, I've noticed once your expiry period lapses your Trial is automatically generated when you logon the next day. However, the repository objects may not necessarily have been cleaned up in a background activity, for example instance ABAP_instance_1 expires on Monday containing the package ZABAP_1. If the user logs on Tuesday and creates a new instance, ABAP_instance_2, they still can reference the package ZABAP_1 from the previous instance and work on the objects for a week or so in the new instance. Then after a spell security authorisations kick in and block the user from accessing the objects under the package ZABAP_1, thus locking the account due to corrupted references.

I was wondering if this has anything to do with the structuring of pods, but you will have a better understanding of what happens under the bonnet, but for the purpose of the discussion, I’m using AWS East Coast(VA).

So that’s the long winded explanation to say, yeah had to blow away the trial instance and manually rebuild instance and everything works now, just got to clone my objects again. No lazy short cuts in the future then!

[Andre_Fischer]

It would have been sufficient to delete the ABAP instance in your trial instance and then recreate it using the booster.

How to delete and re-create your ABAP environment ... - SAP Community

This would trigger the creation of a user on one of the ABAP instances that are used as shared trial instances.

However, deleting the whole trial account also works ;-).

Kind regards,

Andre