New issue
Advanced search Search tips

Issue 653245 link

Starred by 1 user
Status: Verified
Owner:
ntfschr@chromium.org
Closed: Mar 2017
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Feature



Sign in to add a comment

WebView should use new intents for client cert changes

Project Member Reported by ntfschr@chromium.org, Oct 5 2016 
Raised internally as b/30371615

The intent ACTION_STORAGE_CHANGED will be split into 3 intents for the next android release. We are currently filtering for this intent, but should also add in listening for its replacements.

It was suggested in the internal bug that we don't need to listen for all of the new intents, and only need to listen for ACTION_KEY_ACCESS_CHANGED (the new intent that is sent only when access permissions for a private key have changed), in addition to still listening for the current intent.
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 23 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/15710b44fb12849ae9f165bafb934287a349cde6

commit 15710b44fb12849ae9f165bafb934287a349cde6
Author: davidben <davidben@chromium.org>
Date: Thu Mar 23 07:28:44 2017

Use new Keychain intents added in Android O.

ACTION_STORAGE_CHANGED is too spammy and broadcasts on whenever we gain
access to a key in addition to losing access. This means that whenever
the user clicks an auth prompt, we get a notification to drop all
previous selections.

In Android O, the notification is split into finer-grained notifications
with details available to distinguish gaining and losing access. Use
these instead in O.

BUG= 381912 , 653245 

Review-Url: https://codereview.chromium.org/2771543002
Cr-Commit-Position: refs/heads/master@{#459014}

[modify] https://crrev.com/15710b44fb12849ae9f165bafb934287a349cde6/net/android/java/src/org/chromium/net/X509Util.java

Comment 2 by davidben@chromium.org, Mar 23 2017

Status: Fixed (was: Started)

Comment 3 by ntfschr@chromium.org, Aug 24

Status: Verified (was: Fixed)
Bulk edit: marking stale 'fixed' bugs as 'verified' since they don't need verification at this point.
►

Sign in to add a comment