Authenticating Users without Account Linking Google Action
I am attempting to create a Google Action that links to a Libraries resources and allows patrons to retrieve information about their accounts, access the catalog, and place holds. One of the requirements is to have a Google speaker in the library that patrons can walk up to, verbally sign in with their credentials, and then utilize the libraries resources.
All of this functionality works. However, it failed the review process because Google wants me to "implement account linking api" to link patron's accounts to their Google accounts. This (as far as I can tell,) directly contradicts the goal of the project to have a device that anyone can walk up to to sign in with.
My method is indeed against their Policies for Actions on Google. (https://developers.google.com/actions/policies/general-policies#financial_services)
Does anyone have any ideas on how I might achieve the ability to have patrons walk up to a device and sign in while not violating Google's Policies?
actions-on-google
add a comment |
I am attempting to create a Google Action that links to a Libraries resources and allows patrons to retrieve information about their accounts, access the catalog, and place holds. One of the requirements is to have a Google speaker in the library that patrons can walk up to, verbally sign in with their credentials, and then utilize the libraries resources.
All of this functionality works. However, it failed the review process because Google wants me to "implement account linking api" to link patron's accounts to their Google accounts. This (as far as I can tell,) directly contradicts the goal of the project to have a device that anyone can walk up to to sign in with.
My method is indeed against their Policies for Actions on Google. (https://developers.google.com/actions/policies/general-policies#financial_services)
Does anyone have any ideas on how I might achieve the ability to have patrons walk up to a device and sign in while not violating Google's Policies?
actions-on-google
1
In a public setting of that sort, there's no easy way to verbally authenticate. I'd argue that you shouldn't do that, as saying a password aloud is an anti-pattern that others can easily hear. For the sake of security, you may want to take another look at how your action should behave.
– Nick Felker
Nov 21 '18 at 16:50
You are not wrong. However, the desired functionality is as stated, "the ability to have patrons walk up to a device and sign in." If you have suggestions on how to do that with a Google Home device without verbal credential input, that would be helpful.
– Keegan Hare
Nov 29 '18 at 21:09
add a comment |
I am attempting to create a Google Action that links to a Libraries resources and allows patrons to retrieve information about their accounts, access the catalog, and place holds. One of the requirements is to have a Google speaker in the library that patrons can walk up to, verbally sign in with their credentials, and then utilize the libraries resources.
All of this functionality works. However, it failed the review process because Google wants me to "implement account linking api" to link patron's accounts to their Google accounts. This (as far as I can tell,) directly contradicts the goal of the project to have a device that anyone can walk up to to sign in with.
My method is indeed against their Policies for Actions on Google. (https://developers.google.com/actions/policies/general-policies#financial_services)
Does anyone have any ideas on how I might achieve the ability to have patrons walk up to a device and sign in while not violating Google's Policies?
actions-on-google
I am attempting to create a Google Action that links to a Libraries resources and allows patrons to retrieve information about their accounts, access the catalog, and place holds. One of the requirements is to have a Google speaker in the library that patrons can walk up to, verbally sign in with their credentials, and then utilize the libraries resources.
All of this functionality works. However, it failed the review process because Google wants me to "implement account linking api" to link patron's accounts to their Google accounts. This (as far as I can tell,) directly contradicts the goal of the project to have a device that anyone can walk up to to sign in with.
My method is indeed against their Policies for Actions on Google. (https://developers.google.com/actions/policies/general-policies#financial_services)
Does anyone have any ideas on how I might achieve the ability to have patrons walk up to a device and sign in while not violating Google's Policies?
actions-on-google
actions-on-google
asked Nov 21 '18 at 15:00
Keegan Hare
1
1
1
In a public setting of that sort, there's no easy way to verbally authenticate. I'd argue that you shouldn't do that, as saying a password aloud is an anti-pattern that others can easily hear. For the sake of security, you may want to take another look at how your action should behave.
– Nick Felker
Nov 21 '18 at 16:50
You are not wrong. However, the desired functionality is as stated, "the ability to have patrons walk up to a device and sign in." If you have suggestions on how to do that with a Google Home device without verbal credential input, that would be helpful.
– Keegan Hare
Nov 29 '18 at 21:09
add a comment |
1
In a public setting of that sort, there's no easy way to verbally authenticate. I'd argue that you shouldn't do that, as saying a password aloud is an anti-pattern that others can easily hear. For the sake of security, you may want to take another look at how your action should behave.
– Nick Felker
Nov 21 '18 at 16:50
You are not wrong. However, the desired functionality is as stated, "the ability to have patrons walk up to a device and sign in." If you have suggestions on how to do that with a Google Home device without verbal credential input, that would be helpful.
– Keegan Hare
Nov 29 '18 at 21:09
1
1
In a public setting of that sort, there's no easy way to verbally authenticate. I'd argue that you shouldn't do that, as saying a password aloud is an anti-pattern that others can easily hear. For the sake of security, you may want to take another look at how your action should behave.
– Nick Felker
Nov 21 '18 at 16:50
In a public setting of that sort, there's no easy way to verbally authenticate. I'd argue that you shouldn't do that, as saying a password aloud is an anti-pattern that others can easily hear. For the sake of security, you may want to take another look at how your action should behave.
– Nick Felker
Nov 21 '18 at 16:50
You are not wrong. However, the desired functionality is as stated, "the ability to have patrons walk up to a device and sign in." If you have suggestions on how to do that with a Google Home device without verbal credential input, that would be helpful.
– Keegan Hare
Nov 29 '18 at 21:09
You are not wrong. However, the desired functionality is as stated, "the ability to have patrons walk up to a device and sign in." If you have suggestions on how to do that with a Google Home device without verbal credential input, that would be helpful.
– Keegan Hare
Nov 29 '18 at 21:09
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53414840%2fauthenticating-users-without-account-linking-google-action%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53414840%2fauthenticating-users-without-account-linking-google-action%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
In a public setting of that sort, there's no easy way to verbally authenticate. I'd argue that you shouldn't do that, as saying a password aloud is an anti-pattern that others can easily hear. For the sake of security, you may want to take another look at how your action should behave.
– Nick Felker
Nov 21 '18 at 16:50
You are not wrong. However, the desired functionality is as stated, "the ability to have patrons walk up to a device and sign in." If you have suggestions on how to do that with a Google Home device without verbal credential input, that would be helpful.
– Keegan Hare
Nov 29 '18 at 21:09