Skip to content

Conversation

@oskarhane
Copy link
Member

On connect (and at the regular interval) read server config browser.retain_connection_credentials.
If set to a falsy value, remove persisted connection credentials from web browsers localstorage.
Keep in memory to be able to use in a Causal clustered environment where new connections might be opened to run a query on every cluster member (:queries for example).

Show persist status on the :server connect frame.

Connect when set to false:
oskar4j 2017-05-08 at 15 05 26

and true (default):
oskar4j 2017-05-08 at 15 05 02

oskarhane added 2 commits May 8, 2017 15:27
On connect (and at the regular interval) read server config `browser.retain_connection_credentials`.
If set to a falsy value, remove persisted connection credentials from web browsers localstorage.
Keep in memory to be able to use in a Causal clustered environment where new connections might be opened to run a query on every cluster member (`:queries` for example).

Show persist status on the `:server connect` frame.
@oskarhane oskarhane force-pushed the 3.0-store-credentials-config branch from 8ae0d84 to ce64e7e Compare May 8, 2017 13:44
}

// Local vars
let memoryUsername = ''
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@oskarhane I am a bit concerned about having those as local variable, although the current lifecycle of duck files are Ok with that. We may have them in redux store but not synced with local storage.

@irfannuri irfannuri merged commit a6cb25c into neo4j:3.0 May 18, 2017
@oskarhane oskarhane deleted the 3.0-store-credentials-config branch August 1, 2017 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants