This hits close to home. Back when I worked at Oracle, I was doing work with ODSEE (an LDAP server) on an application platform. Despite working at Oracle for an Oracle team (not a contractor or...
Requiring some kind of registration or login to access your API documentation also prevents your competition from examining your API and learning from it. No competitors have ever thought to register using their home address, or to share a password from a friend, right? Never. They're not that smart. It could never possibly happen. You would certainly never do that, so why would they?
This hits close to home. Back when I worked at Oracle, I was doing work with ODSEE (an LDAP server) on an application platform. Despite working at Oracle for an Oracle team (not a contractor or anything), only 1 person on our team had access to documentation, and we had to pay for access, per person. Nobody used ODSEE in 2018, so of course whenever I ran into a problem, there were no Server Fault or Stack Overflow questions about it - just an Oracle support article describing my exact error, and you had to pay for access to view anything beyond the description.
This hits close to home. Back when I worked at Oracle, I was doing work with ODSEE (an LDAP server) on an application platform. Despite working at Oracle for an Oracle team (not a contractor or anything), only 1 person on our team had access to documentation, and we had to pay for access, per person. Nobody used ODSEE in 2018, so of course whenever I ran into a problem, there were no Server Fault or Stack Overflow questions about it - just an Oracle support article describing my exact error, and you had to pay for access to view anything beyond the description.