Yes, at the moment the we only support receiving a token provided in the
Authentication header field. We don't provide the standard endpoints for
token acquisition and refresh.
On Fri, Oct 4, 2019 at 4:14 PM John Blum wrote:
> So application developer's will need to know to code their applicatio
got it
On Mon, Oct 7, 2019 at 10:33 AM Joris Melchior wrote:
> Yes, at the moment the we only support receiving a token provided in the
> Authentication header field. We don't provide the standard endpoints for
> token acquisition and refresh.
>
> On Fri, Oct 4, 2019 at 4:14 PM John Blum wrote:
Bump - reminder for folks to consider these two changes be included in
Geode 1.9.2
Thanks
--Jens
On Fri, Oct 4, 2019 at 12:57 PM Juan José Ramos wrote:
> +1
>
> On Fri, Oct 4, 2019 at 6:44 PM Jens Deppe wrote:
>
> > I'd like to propose adding these two fixes to release/1.9.2
> >
> > GEODE-7261
I don’t yet have a clear understanding of what makes these critical,
especially GEODE-7241. Can you elaborate, including:
* Are these fixes already in 1.10? If not, would a 1.10.1 patch be
required as well?
* What is the impact of not including each of these fixes? Is there a
workaround?
On Fri,
Hi there Owen,
I apologize if it is not clear.
GEODE-7241 is a regression where the published artifact "geode-web" and
"geode-web-api" were published as jars and not wars.
NOW, why is it critical for 1.9.x... Well, the answer is fairly short.
In Spring Data Geode, there is an ability to star
Sounds like a big win for convenience, and clearly a regression relative to the
last release of Geode that SBDG picked up (1.6). Thanks for clarifying what is
at stake.
+1 for including both fixes
> On Oct 7, 2019, at 4:50 PM, Udo Kohlmeyer wrote:
>
> Hi there Owen,
>
> I apologize if it is
