apexguy wrote:Can you provide a link to where this limitation is documented? Or explain why you think this is the case?
I have created a custom authentication scheme, assigned it to my app and by all accounts, save one, it is working well. The only issue I have, is that I have several interactive reports, and as part of this, the actions button has some features that are unavailable to me because I am using custom authentication. One such feature is the ability to "Save Report" which works if you use standard APEX and/or database authentication
apexguy wrote:Two things:
The authentication is working... this is a production system at the moment. But the capability to save IR's doesn't exist within the actions menu. I'm not sure what dictates this.
If you have this working then I would ask if I could see how you setup your custom authentication. I do have one question. You say you created a apex user account, tried it and you can save IR's. You then said you switched to custom authentication and it still works with the username. May I suggest you remove the username from apex BEFORE switching to custom authentication. I do not have any users saved in the apex repository. I'm wondering if yours is working because you still have the user info saved in the apex repository and because of this the option is still available to you.Not so. Interactive reports can be saved following custom authentication using a username with no corresponding APEX user.