| 2015-12-11 16:41:04 |
Dave Chen |
bug |
|
|
added bug |
| 2015-12-11 16:41:37 |
Dave Chen |
description |
Currently, IdP doesn't support to filter the DB records based on the field, for example,
If configure the DB like this,
mysql> select * from identity_provider;
+------+---------+-------------+
| id | enabled | description |
+------+---------+-------------+
| idp1 | 1 | NULL |
| idp2 | 1 | NULL |
+------+---------+-------------+
2 rows in set (0.00 sec)
And I query the IdP by this curl, I get all of the records from DB,
curl -g -i -X GET http://127.0.0.1:35357/v3/OS-FEDERATION/identity_providers?id=idontexist -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H "X-Auth-Token: f74ac35177cb4720891a9cfed5ea1b9c"
{
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers?id=idp1",
"previous": null,
"next": null
},
"identity_providers": [{
"remote_ids": [],
"enabled": true,
"id": "idp1",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1/protocols"
},
"description": null
}, {
"remote_ids": [],
"enabled": true,
"id": "idp2",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2/protocols"
},
"description": null
}]
}
This feature should be supported since OSC depends on this to filter the DB records wanted.
Noted: Open this bug since it's different with https://bugs.launchpad.net/python-openstackclient/+bug/1479837, they are two different things, and I think this more sound like a feature that keystone should support. |
Currently, IdP doesn't support to filter the DB records based on the field, for example,
If configure the DB like this,
mysql> select * from identity_provider;
+------+---------+-------------+
| id | enabled | description |
+------+---------+-------------+
| idp1 | 1 | NULL |
| idp2 | 1 | NULL |
+------+---------+-------------+
2 rows in set (0.00 sec)
And I query the IdP by this curl, I get all of the records from DB,
curl -g -i -X GET http://127.0.0.1:35357/v3/OS-FEDERATION/identity_providers?id=idontexist -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H "X-Auth-Token: f74ac35177cb4720891a9cfed5ea1b9c"
{
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers?id=idp1",
"previous": null,
"next": null
},
"identity_providers": [{
"remote_ids": [],
"enabled": true,
"id": "idp1",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1/protocols"
},
"description": null
}, {
"remote_ids": [],
"enabled": true,
"id": "idp2",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2/protocols"
},
"description": null
}]
}
This feature should be supported since OSC depends on this to filter the DB records wanted.
Noted: Open this bug since it's different with https://bugs.launchpad.net/python-openstackclient/+bug/1479837, they are two different things, and I think this more sound like a feature that keystone should support. |
|
| 2015-12-11 16:41:41 |
Dave Chen |
python-openstackclient: assignee |
|
Dave Chen (wei-d-chen) |
|
| 2015-12-11 17:34:35 |
Dave Chen |
affects |
python-openstackclient |
keystone |
|
| 2015-12-11 17:59:29 |
Dave Chen |
description |
Currently, IdP doesn't support to filter the DB records based on the field, for example,
If configure the DB like this,
mysql> select * from identity_provider;
+------+---------+-------------+
| id | enabled | description |
+------+---------+-------------+
| idp1 | 1 | NULL |
| idp2 | 1 | NULL |
+------+---------+-------------+
2 rows in set (0.00 sec)
And I query the IdP by this curl, I get all of the records from DB,
curl -g -i -X GET http://127.0.0.1:35357/v3/OS-FEDERATION/identity_providers?id=idontexist -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H "X-Auth-Token: f74ac35177cb4720891a9cfed5ea1b9c"
{
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers?id=idp1",
"previous": null,
"next": null
},
"identity_providers": [{
"remote_ids": [],
"enabled": true,
"id": "idp1",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1/protocols"
},
"description": null
}, {
"remote_ids": [],
"enabled": true,
"id": "idp2",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2/protocols"
},
"description": null
}]
}
This feature should be supported since OSC depends on this to filter the DB records wanted.
Noted: Open this bug since it's different with https://bugs.launchpad.net/python-openstackclient/+bug/1479837, they are two different things, and I think this more sound like a feature that keystone should support. |
Currently, IdP doesn't support to filter the DB records based on the field, for example,
If configure the DB like this,
mysql> select * from identity_provider;
+------+---------+-------------+
| id | enabled | description |
+------+---------+-------------+
| idp1 | 1 | NULL |
| idp2 | 1 | NULL |
+------+---------+-------------+
2 rows in set (0.00 sec)
And I query the IdP by this curl, I get all of the records from DB,
curl -g -i -X GET http://127.0.0.1:35357/v3/OS-FEDERATION/identity_providers?id=idontexist -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H "X-Auth-Token: f74ac35177cb4720891a9cfed5ea1b9c"
{
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers?id=idp1",
"previous": null,
"next": null
},
"identity_providers": [{
"remote_ids": [],
"enabled": true,
"id": "idp1",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1/protocols"
},
"description": null
}, {
"remote_ids": [],
"enabled": true,
"id": "idp2",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2/protocols"
},
"description": null
}]
}
This feature should be supported since OSC depends on this to filter the DB records that is wanted.
Noted: Open this bug since it's different with https://bugs.launchpad.net/python-openstackclient/+bug/1479837, they are two different things, and I think this more sound like a feature that keystone should support. |
|
| 2015-12-11 22:19:12 |
Dave Chen |
description |
Currently, IdP doesn't support to filter the DB records based on the field, for example,
If configure the DB like this,
mysql> select * from identity_provider;
+------+---------+-------------+
| id | enabled | description |
+------+---------+-------------+
| idp1 | 1 | NULL |
| idp2 | 1 | NULL |
+------+---------+-------------+
2 rows in set (0.00 sec)
And I query the IdP by this curl, I get all of the records from DB,
curl -g -i -X GET http://127.0.0.1:35357/v3/OS-FEDERATION/identity_providers?id=idontexist -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H "X-Auth-Token: f74ac35177cb4720891a9cfed5ea1b9c"
{
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers?id=idp1",
"previous": null,
"next": null
},
"identity_providers": [{
"remote_ids": [],
"enabled": true,
"id": "idp1",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1/protocols"
},
"description": null
}, {
"remote_ids": [],
"enabled": true,
"id": "idp2",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2/protocols"
},
"description": null
}]
}
This feature should be supported since OSC depends on this to filter the DB records that is wanted.
Noted: Open this bug since it's different with https://bugs.launchpad.net/python-openstackclient/+bug/1479837, they are two different things, and I think this more sound like a feature that keystone should support. |
Currently, IdP doesn't support to filter the DB records based on the field, for example,
If config the DB like this,
mysql> select * from identity_provider;
+------+---------+-------------+
| id | enabled | description |
+------+---------+-------------+
| idp1 | 1 | NULL |
| idp2 | 1 | NULL |
+------+---------+-------------+
2 rows in set (0.00 sec)
And I query the IdP by this curl, I get all of the records from DB,
curl -g -i -X GET http://127.0.0.1:35357/v3/OS-FEDERATION/identity_providers?id=idontexist -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H "X-Auth-Token: f74ac35177cb4720891a9cfed5ea1b9c"
{
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers?id=idp1",
"previous": null,
"next": null
},
"identity_providers": [{
"remote_ids": [],
"enabled": true,
"id": "idp1",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1/protocols"
},
"description": null
}, {
"remote_ids": [],
"enabled": true,
"id": "idp2",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2/protocols"
},
"description": null
}]
}
This feature should be supported since OSC depends on this to filter the DB records that is wanted.
Noted: Open this bug since it's different with https://bugs.launchpad.net/python-openstackclient/+bug/1479837, they are two different things, and I think this sound like a feature that keystone should support. |
|
| 2015-12-12 00:46:38 |
OpenStack Infra |
keystone: status |
New |
In Progress |
|
| 2015-12-13 07:58:01 |
Dave Chen |
description |
Currently, IdP doesn't support to filter the DB records based on the field, for example,
If config the DB like this,
mysql> select * from identity_provider;
+------+---------+-------------+
| id | enabled | description |
+------+---------+-------------+
| idp1 | 1 | NULL |
| idp2 | 1 | NULL |
+------+---------+-------------+
2 rows in set (0.00 sec)
And I query the IdP by this curl, I get all of the records from DB,
curl -g -i -X GET http://127.0.0.1:35357/v3/OS-FEDERATION/identity_providers?id=idontexist -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H "X-Auth-Token: f74ac35177cb4720891a9cfed5ea1b9c"
{
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers?id=idp1",
"previous": null,
"next": null
},
"identity_providers": [{
"remote_ids": [],
"enabled": true,
"id": "idp1",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1/protocols"
},
"description": null
}, {
"remote_ids": [],
"enabled": true,
"id": "idp2",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2/protocols"
},
"description": null
}]
}
This feature should be supported since OSC depends on this to filter the DB records that is wanted.
Noted: Open this bug since it's different with https://bugs.launchpad.net/python-openstackclient/+bug/1479837, they are two different things, and I think this sound like a feature that keystone should support. |
Currently, IdP doesn't support to filter the DB records based on the field, for example,
If config the DB like this,
mysql> select * from identity_provider;
+------+---------+-------------+
| id | enabled | description |
+------+---------+-------------+
| idp1 | 1 | NULL |
| idp2 | 1 | NULL |
+------+---------+-------------+
2 rows in set (0.00 sec)
And I query the IdP by this curl, I get all of the records from DB,
curl -g -i -X GET http://127.0.0.1:35357/v3/OS-FEDERATION/identity_providers?id=idp1 -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H "X-Auth-Token: f74ac35177cb4720891a9cfed5ea1b9c"
{
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers?id=idp1",
"previous": null,
"next": null
},
"identity_providers": [{
"remote_ids": [],
"enabled": true,
"id": "idp1",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp1/protocols"
},
"description": null
}, {
"remote_ids": [],
"enabled": true,
"id": "idp2",
"links": {
"self": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2",
"protocols": "http://10.239.48.36:35357/v3/OS-FEDERATION/identity_providers/idp2/protocols"
},
"description": null
}]
}
This feature should be supported since OSC depends on this to filter the DB records that is wanted.
Noted: Open this bug since it's different with https://bugs.launchpad.net/python-openstackclient/+bug/1479837, they are two different things, and I think this sound like a feature that keystone should support. |
|
| 2015-12-29 20:12:08 |
OpenStack Infra |
keystone: assignee |
Dave Chen (wei-d-chen) |
Henry Nash (henry-nash) |
|
| 2016-01-12 07:50:59 |
OpenStack Infra |
keystone: assignee |
Henry Nash (henry-nash) |
Dave Chen (wei-d-chen) |
|
| 2016-01-19 17:45:55 |
OpenStack Infra |
keystone: status |
In Progress |
Fix Released |
|
| 2016-02-21 07:25:40 |
Steve Martinelli |
keystone: importance |
Undecided |
Medium |
|
