Connector assumes username and subdomain should be same about loopback-connector-cloudant HOT 12 CLOSED

@ssh24 Thanks for the info. So I will wait for the product bugfix :)
Thanks for your help.

from loopback-connector-cloudant.

I believe it's same as #68
@ufuf PTAL. Thanks.

from loopback-connector-cloudant.

@ufuf When you have another user that does not have the admin role, but has some sort of read, create, etc... permission on the database, you can use the CLOUDANT_URL env variable to set the url or set the url on the datasource config as well. For more information, please read the docs on how to use url vs username vs password.

Closing this issue, feel free to reopen if you have any questions.

from loopback-connector-cloudant.

@ssh24 I updated the connectors but still getting the error.
My configuration is [email protected], [email protected], [email protected]
And my config is attached.

from loopback-connector-cloudant.

Sorry, @ufuf I thought the fix was already in 1.x. Reopening this issue and backporting the fix. Thank you for your patience.

from loopback-connector-cloudant.

@ufuf Ignore my previous comment. Tried reproducing and the fix is already in 1.x.

Did you check the _admin role for the user you are giving the access to? Please check off the _admin role and try again.

Closing this issue in this case. Feel free to reopen if you have any questions.

from loopback-connector-cloudant.

@ssh24 it seems off. My permissions screen is like this:

from loopback-connector-cloudant.

@ufuf You need to check off the _admin role to the user in blue.

from loopback-connector-cloudant.

@ssh24 it is already off. only reader and writer attributes are selected.

from loopback-connector-cloudant.

Sorry, I meant to check it on.

from loopback-connector-cloudant.

I checked it on. Right now all the checkboxes are selected. But in Api Designer I am still getting error while trying to connect.

from loopback-connector-cloudant.

@ufuf I can reproduce the above issue. But it is a apic bug rather than cloudant. I will file a bug in apic end to get this looked into asap.

In order to know it is not a cloudant bug, you can create a boot script and run it. It works with the custom user with _admin privileges.

/server/boot/script.js

'use strict';
var async = require('async');
var _ = require('lodash');
var util = require('util');

module.exports = function(app) {
  var db = app.dataSources.cloudantDS;
  var Car = app.models.Car;

  db.automigrate(function(err) {
    if (err) throw err;
    Car.create([{Model: 'Toyota', Year: 2005}, {Model: 'Audi', Year: 2014}],
  function(err, result) {
    if (err) throw err;
    console.log('Create: ' + JSON.stringify(result));
  });
  });
};

Hope this helps you.

Also, thank you for helping us finding a bug on the product side. :)

from loopback-connector-cloudant.