René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Authentication and Authorization for feast serving","articleBody":"**Is your feature request related to a problem? Please describe.**\r\nCurrently user authentication and authorization limits access to Feast core(#793 ), but doesn't secure feast serving. Since feast client connects to core and serving directly, authentication and authorization on feast serving is a necessary feature. \r\n**Describe the solution you'd like**\r\nThe PR #793, implements jwt authenticator and Keto authorizer for feast core. Same implementation will be done on the feast serving. Instead of replicating the code, Authorization and authentication will be moved separate module feast-auth, which will be included as a dependency in feast core and feast serving. Rest of the configuration will remain same as described in the documentation for #793. Python sdk will be updated to use secure channel to connect to feast serving. \r\n\r\n**Assumptions:**\r\n- User authentication and authorization only applies to Feast Core and serving not ingestion.\r\n\r\n**Out of scope:**\r\n- Go and java clients.\r\n\r\n**Describe alternatives you've considered**\r\nRefer to issue #793 for the alternatives considered.\r\n","author":{"url":"https://github.com/jmelinav","@type":"Person","name":"jmelinav"},"datePublished":"2020-06-23T17:29:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/823/feast/issues/823"}