On Thu, Apr 26, 2018 at 8:02 PM, Tom Pantelis <tompante...@gmail.com> wrote:
> On Thu, Apr 26, 2018 at 1:57 PM, FREEMAN, BRIAN D <bf1...@att.com> wrote: > >> How would that affect end users (if at all) ? >> > > It wouldn't unless an end user doesn't want authentication which I doubt > anyone would in production. All other rest endpoints in ODL (that I know > of) only support authenticated. > JUST for the sake of completeness (this is NOT relevant in this specific context being discussed here!), I'll have to throw in here that we just introduced ;) a new web endpoint named /diagstatus which is public and not authenticated; full details in https://jira.opendaylight.org/browse/INFRAUTILS-33. > brian > >> >> >> *From:* controller-dev-boun...@lists.opendaylight.org < >> controller-dev-boun...@lists.opendaylight.org> *On Behalf Of *Tom >> Pantelis >> *Sent:* Thursday, April 26, 2018 1:55 PM >> *To:* netconf-dev <netconf-...@lists.opendaylight.org>; controller-dev < >> controller-dev@lists.opendaylight.org> >> *Subject:* [controller-dev] Restconf no-auth features >> >> >> >> Hello, >> >> >> >> I am in the process of converting restconf to use the new web API in aaa >> in lieu of the web.xml files. Supporting no-auth is a bit of a pain. I have >> maintained no-auth support for the current draft02 restconf endpoint for >> legacy. However I'd like to drop no-auth for the new(er) rfc8040 endpoint >> to simplify. Any objections? >> >> >> >> Tom >> > > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev