I have documentation that is for Customers only (i.e. should not be exposed on the Internet). My customers are going to access the documentation as READ-ONLY from within our application after logging into our app.
We don't have any SSO. The solution I have thought of is to have the in-app link to the documentation use a reserved login (i.e. some system account we create) so that it's authenticated, but doesn't require the customer to log in.
Is this in violation of any licensing?
Is there any technical concerns? For example, is it possible to overload one login with too many concurrent sessions versus spreading the sessions over individual logins?
Thanks.
-Roger