Re: If the authenticationEnabled is true Ignite web control conneced failed

[Alexey Kuznetsov]

Actually, IGNITE-8428 already in master and will be released together with
Ignite-2.7.
As for https://console.gridgain.com  it may be updated in the beginning of
August.

On Thu, Jul 26, 2018 at 6:17 AM Denis Magda  wrote:

> Alexey K.,
>
> Please shed some light on when the secured cluster support will be
> released? I know it's already ready and just waiting its time to see the
> world.
>
> --
> Denis
>
> On Wed, Jul 25, 2018 at 6:34 AM ezhuravlev 
> wrote:
>
>> As for now, web agent can't connect to the secure Ignite cluster, this
>> functionality should be available with version 2.7
>>
>> Evgenii
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>> --
>> Alexey Kuznetsov
>> 
>>
>

Re: If the authenticationEnabled is true Ignite web control conneced failed

[Denis Magda]

Alexey K.,

Please shed some light on when the secured cluster support will be
released? I know it's already ready and just waiting its time to see the
world.

--
Denis

On Wed, Jul 25, 2018 at 6:34 AM ezhuravlev  wrote:

> As for now, web agent can't connect to the secure Ignite cluster, this
> functionality should be available with version 2.7
>
> Evgenii
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: If the authenticationEnabled is true Ignite web control conneced failed

[ezhuravlev]

As for now, web agent can't connect to the secure Ignite cluster, this
functionality should be available with version 2.7

Evgenii



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

If the authenticationEnabled is true Ignite web control conneced failed

[hulitao198758]

If the  attribute is
opened, an error is reported when starting the monitoring cluster using the
official web control platform

Agent configuration:
User's security tokens: 5NfQ
URI to Ignite node REST server: http://127.0.0.1:9380
URI to Ignite Console server  : https://console.gridgain.com
Path to agent property file   : default.properties
Path to JDBC drivers folder   :
/Users/hulitao/Documents/apache-ignite-fabric-2.3.0-bin/ignite-web-agent-2.3.2/jdbc-drivers
Demo mode : enabled

[2018-07-23 11:50:02,602][INFO ][main][AgentLauncher] Connecting to:
https://console.gridgain.com
[2018-07-23 11:50:04,046][INFO ][EventThread][AgentLauncher] Connection
established.
[2018-07-23 11:50:05,072][INFO ][EventThread][AgentLauncher] Authentication
success.
[2018-07-23 11:50:05,145][WARN ][pool-1-thread-1][ClusterListener] Failed to
handle request - session token not found or invalid
[2018-07-23 12:01:10,000][ERROR][EventThread][AgentLauncher] Connection
error.
io.socket.engineio.client.EngineIOException: websocket error
at io.socket.engineio.client.Transport.onError(Transport.java:71)
at
io.socket.engineio.client.transports.WebSocket.access$400(WebSocket.java:24)
at
io.socket.engineio.client.transports.WebSocket$2$5.run(WebSocket.java:135)
at io.socket.thread.EventThread$2.run(EventThread.java:80)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.EOFException
at okio.RealBufferedSource.require(RealBufferedSource.java:59)
at okio.RealBufferedSource.readByte(RealBufferedSource.java:72)
at 
okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.java:113)
at
okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:97)
at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:262)
at 
okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:201)
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:141)
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
... 3 more




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/