user2989656
user2989656

Reputation: 11

Chrome Extension permissions field in the manifest.json

I'm trying narrow the scope of permission, so that I don't have to do the following in the manifest file.

"permissions": ["http://*.google.com/", "https://*.google.com/"],

However, the authentication requires www.google.com, login.google.com and more.

My first question would be: is having "http://*.google.com/", "https://*.google.com/" in the permissions field a bad practice?

If yes, what are my options? I looked at using "identity", but does it apply to extensions as well?

Upvotes: 0

Views: 4910

Answers (1)

KimKha
KimKha

Reputation: 4510

I'm not sure about your question. Please provide more details about what you really want. So, I firstly give some info, maybe it right.

Use:

"permissions": ["*://*.google.com/"]

Pages accepted:

Use:

"permissions": ["*://www.google.com/"]

Page accepted:

You can get more info in Chrome Extension Pattern page.

Upvotes: 1

Related Questions