[jira] [Commented] (DIRSERVER-2203) Server crashed, data repair completed but no data shows up in ADS
[ https://issues.apache.org/jira/browse/DIRSERVER-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098575#comment-16098575 ] Emmanuel Lecharny commented on DIRSERVER-2203: -- There is no much more you can do thn starting up with a blank database and inject a LDIF backup into it atm :/ > Server crashed, data repair completed but no data shows up in ADS > - > > Key: DIRSERVER-2203 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2203 > Project: Directory ApacheDS > Issue Type: Bug >Reporter: Guillaume Lefranc > > Hi, > we recently had one of our ADS server suffering a power loss. On restart the > DB was successfully repaired but our root DN data doesn't show up. The > toplevel DN shows up but nothing under it. > However the entries in our root DN seem to have been repaired somehow > according to the logs: > INFO | jvm 1| 2017/07/20 10:19:17 | Service started. > INFO | jvm 1| 2017/07/20 10:19:17 | Repairing the database. > INFO | jvm 1| 2017/07/20 10:19:17 | Repairing partition dir > /var/lib/apacheds-2.0.0-M23/default/partitions > INFO | jvm 1| 2017/07/20 10:19:21 | Re-building indices... > INFO | jvm 1| 2017/07/20 10:19:21 | Read entry cn=eng with ID > 111f527f-5cdd-4133-87e3-ddfaaaf0db97 and parent ID > 6311d9b9-5833-437e-8a1a-d2a96596f75b > INFO | jvm 1| 2017/07/20 10:19:21 | Read entry uid=mg with ID > 1188dbf7-be5b-43e3-97d1-2cc32de8f0c6 and parent ID > 4cf26ac6-0e62-4a7e-883d-6661da47071c > INFO | jvm 1| 2017/07/20 10:19:21 | Read entry uid=yg with ID > 39a90b24-f4de-4dae-9473-bce54a52df52 and parent ID > 4cf26ac6-0e62-4a7e-883d-6661da47071c > INFO | jvm 1| 2017/07/20 10:19:21 | Read entry uid=mk with ID > 3cf2b57b-f533-4dfb-ab1f-ceb8f57fd16e and parent ID > 4cf26ac6-0e62-4a7e-883d-6661da47071c > INFO | jvm 1| 2017/07/20 10:19:21 | Read entry cn=ops with ID > 3cf697e3-913b-4ee5-88c7-b74927300cf0 and parent ID > 6311d9b9-5833-437e-8a1a-d2a96596f75b > ... truncated ... > INFO | jvm 1| 2017/07/20 10:19:21 | Updating the RDN index counters... > INFO | jvm 1| 2017/07/20 10:19:22 | Total entries present in the > partition 34 > INFO | jvm 1| 2017/07/20 10:19:22 | Repair complete > INFO | jvm 1| 2017/07/20 10:19:22 | Database repaired. > Please advise. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DIRSERVER-2203) Server crashed, data repair completed but no data shows up in ADS
[ https://issues.apache.org/jira/browse/DIRSERVER-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098476#comment-16098476 ] Guillaume Lefranc commented on DIRSERVER-2203: -- ADS version: 2.0.0-M23 > Server crashed, data repair completed but no data shows up in ADS > - > > Key: DIRSERVER-2203 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2203 > Project: Directory ApacheDS > Issue Type: Bug >Reporter: Guillaume Lefranc > > Hi, > we recently had one of our ADS server suffering a power loss. On restart the > DB was successfully repaired but our root DN data doesn't show up. The > toplevel DN shows up but nothing under it. > However the entries in our root DN seem to have been repaired somehow > according to the logs: > INFO | jvm 1| 2017/07/20 10:19:17 | Service started. > INFO | jvm 1| 2017/07/20 10:19:17 | Repairing the database. > INFO | jvm 1| 2017/07/20 10:19:17 | Repairing partition dir > /var/lib/apacheds-2.0.0-M23/default/partitions > INFO | jvm 1| 2017/07/20 10:19:21 | Re-building indices... > INFO | jvm 1| 2017/07/20 10:19:21 | Read entry cn=eng with ID > 111f527f-5cdd-4133-87e3-ddfaaaf0db97 and parent ID > 6311d9b9-5833-437e-8a1a-d2a96596f75b > INFO | jvm 1| 2017/07/20 10:19:21 | Read entry uid=mg with ID > 1188dbf7-be5b-43e3-97d1-2cc32de8f0c6 and parent ID > 4cf26ac6-0e62-4a7e-883d-6661da47071c > INFO | jvm 1| 2017/07/20 10:19:21 | Read entry uid=yg with ID > 39a90b24-f4de-4dae-9473-bce54a52df52 and parent ID > 4cf26ac6-0e62-4a7e-883d-6661da47071c > INFO | jvm 1| 2017/07/20 10:19:21 | Read entry uid=mk with ID > 3cf2b57b-f533-4dfb-ab1f-ceb8f57fd16e and parent ID > 4cf26ac6-0e62-4a7e-883d-6661da47071c > INFO | jvm 1| 2017/07/20 10:19:21 | Read entry cn=ops with ID > 3cf697e3-913b-4ee5-88c7-b74927300cf0 and parent ID > 6311d9b9-5833-437e-8a1a-d2a96596f75b > ... truncated ... > INFO | jvm 1| 2017/07/20 10:19:21 | Updating the RDN index counters... > INFO | jvm 1| 2017/07/20 10:19:22 | Total entries present in the > partition 34 > INFO | jvm 1| 2017/07/20 10:19:22 | Repair complete > INFO | jvm 1| 2017/07/20 10:19:22 | Database repaired. > Please advise. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (DIRSERVER-2203) Server crashed, data repair completed but no data shows up in ADS
Guillaume Lefranc created DIRSERVER-2203: Summary: Server crashed, data repair completed but no data shows up in ADS Key: DIRSERVER-2203 URL: https://issues.apache.org/jira/browse/DIRSERVER-2203 Project: Directory ApacheDS Issue Type: Bug Reporter: Guillaume Lefranc Hi, we recently had one of our ADS server suffering a power loss. On restart the DB was successfully repaired but our root DN data doesn't show up. The toplevel DN shows up but nothing under it. However the entries in our root DN seem to have been repaired somehow according to the logs: INFO | jvm 1| 2017/07/20 10:19:17 | Service started. INFO | jvm 1| 2017/07/20 10:19:17 | Repairing the database. INFO | jvm 1| 2017/07/20 10:19:17 | Repairing partition dir /var/lib/apacheds-2.0.0-M23/default/partitions INFO | jvm 1| 2017/07/20 10:19:21 | Re-building indices... INFO | jvm 1| 2017/07/20 10:19:21 | Read entry cn=eng with ID 111f527f-5cdd-4133-87e3-ddfaaaf0db97 and parent ID 6311d9b9-5833-437e-8a1a-d2a96596f75b INFO | jvm 1| 2017/07/20 10:19:21 | Read entry uid=mg with ID 1188dbf7-be5b-43e3-97d1-2cc32de8f0c6 and parent ID 4cf26ac6-0e62-4a7e-883d-6661da47071c INFO | jvm 1| 2017/07/20 10:19:21 | Read entry uid=yg with ID 39a90b24-f4de-4dae-9473-bce54a52df52 and parent ID 4cf26ac6-0e62-4a7e-883d-6661da47071c INFO | jvm 1| 2017/07/20 10:19:21 | Read entry uid=mk with ID 3cf2b57b-f533-4dfb-ab1f-ceb8f57fd16e and parent ID 4cf26ac6-0e62-4a7e-883d-6661da47071c INFO | jvm 1| 2017/07/20 10:19:21 | Read entry cn=ops with ID 3cf697e3-913b-4ee5-88c7-b74927300cf0 and parent ID 6311d9b9-5833-437e-8a1a-d2a96596f75b ... truncated ... INFO | jvm 1| 2017/07/20 10:19:21 | Updating the RDN index counters... INFO | jvm 1| 2017/07/20 10:19:22 | Total entries present in the partition 34 INFO | jvm 1| 2017/07/20 10:19:22 | Repair complete INFO | jvm 1| 2017/07/20 10:19:22 | Database repaired. Please advise. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (DIRKRB-636) NPE in GssInitCred when a tgt is obtained via JAAS
[ https://issues.apache.org/jira/browse/DIRKRB-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved DIRKRB-636. Resolution: Fixed > NPE in GssInitCred when a tgt is obtained via JAAS > -- > > Key: DIRKRB-636 > URL: https://issues.apache.org/jira/browse/DIRKRB-636 > Project: Directory Kerberos > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.1.0 > > > There is a NPE in GssInitCred when a TGT is obtained via JAAS, as we have no > "name" in GssInitCred.getInstance. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (DIRKRB-636) NPE in GssInitCred when a tgt is obtained via JAAS
Colm O hEigeartaigh created DIRKRB-636: -- Summary: NPE in GssInitCred when a tgt is obtained via JAAS Key: DIRKRB-636 URL: https://issues.apache.org/jira/browse/DIRKRB-636 Project: Directory Kerberos Issue Type: Bug Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.1.0 There is a NPE in GssInitCred when a TGT is obtained via JAAS, as we have no "name" in GssInitCred.getInstance. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-571) Add encryptRaw interface for GssToken encryption
[ https://issues.apache.org/jira/browse/DIRKRB-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-571: --- Fix Version/s: 1.1.0 > Add encryptRaw interface for GssToken encryption > > > Key: DIRKRB-571 > URL: https://issues.apache.org/jira/browse/DIRKRB-571 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > Attachments: DIRKRB-571-V1.patch > > > encryptRaw encrypts data without adding confounder, padding and checksum. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-576) Add test for client-server based on Kerby GssApi
[ https://issues.apache.org/jira/browse/DIRKRB-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-576: --- Fix Version/s: 1.1.0 > Add test for client-server based on Kerby GssApi > > > Key: DIRKRB-576 > URL: https://issues.apache.org/jira/browse/DIRKRB-576 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > Attachments: DIRKRB-576-V1.patch > > > Client and App server communication test based on Kerby GssApi implementation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-581) Imcompatible token header in init context against JDK GssApi
[ https://issues.apache.org/jira/browse/DIRKRB-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-581: --- Fix Version/s: 1.1.0 > Imcompatible token header in init context against JDK GssApi > > > Key: DIRKRB-581 > URL: https://issues.apache.org/jira/browse/DIRKRB-581 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > Attachments: DIRKRB-581-V1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-560) Implement GSSContextSpi interface
[ https://issues.apache.org/jira/browse/DIRKRB-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-560: --- Fix Version/s: 1.1.0 > Implement GSSContextSpi interface > - > > Key: DIRKRB-560 > URL: https://issues.apache.org/jira/browse/DIRKRB-560 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > Attachments: DIRKRB-560-V1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-566) Implement Gss tokens defined in RFC 1964
[ https://issues.apache.org/jira/browse/DIRKRB-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-566: --- Fix Version/s: 1.1.0 > Implement Gss tokens defined in RFC 1964 > > > Key: DIRKRB-566 > URL: https://issues.apache.org/jira/browse/DIRKRB-566 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > Attachments: DIRKRB-566-V1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-559) Validataion of ApReq and ApRep message in peer node
[ https://issues.apache.org/jira/browse/DIRKRB-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-559: --- Fix Version/s: 1.1.0 > Validataion of ApReq and ApRep message in peer node > --- > > Key: DIRKRB-559 > URL: https://issues.apache.org/jira/browse/DIRKRB-559 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > Attachments: DIRKRB-559-V1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-568) Using RFC 4121 tokens in KerbyContext
[ https://issues.apache.org/jira/browse/DIRKRB-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-568: --- Fix Version/s: 1.1.0 > Using RFC 4121 tokens in KerbyContext > - > > Key: DIRKRB-568 > URL: https://issues.apache.org/jira/browse/DIRKRB-568 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > Attachments: DIRKRB-568-V1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-582) Implement checksum calculation for Authenticator in ApRequest
[ https://issues.apache.org/jira/browse/DIRKRB-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-582: --- Fix Version/s: 1.1.0 > Implement checksum calculation for Authenticator in ApRequest > - > > Key: DIRKRB-582 > URL: https://issues.apache.org/jira/browse/DIRKRB-582 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou > Fix For: 1.1.0 > > > Item 'cksum' of Authenticator is verified in JDK under certain conditions, > but it's not provided in Kerby while generating Authenticator. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-565) Implement Gss tokens defined in RFC 4121
[ https://issues.apache.org/jira/browse/DIRKRB-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-565: --- Fix Version/s: 1.1.0 > Implement Gss tokens defined in RFC 4121 > > > Key: DIRKRB-565 > URL: https://issues.apache.org/jira/browse/DIRKRB-565 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > Attachments: DIRKRB-565-V1.patch, DIRKRB-565-V2.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-555) Implement GSSNameSpi interface
[ https://issues.apache.org/jira/browse/DIRKRB-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-555: --- Fix Version/s: 1.1.0 > Implement GSSNameSpi interface > -- > > Key: DIRKRB-555 > URL: https://issues.apache.org/jira/browse/DIRKRB-555 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > Attachments: DIRKRB-555-V1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-535) Implementing GSSAPI module based on Kerby Kerberos library
[ https://issues.apache.org/jira/browse/DIRKRB-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-535: --- Fix Version/s: 1.1.0 > Implementing GSSAPI module based on Kerby Kerberos library > -- > > Key: DIRKRB-535 > URL: https://issues.apache.org/jira/browse/DIRKRB-535 > Project: Directory Kerberos > Issue Type: New Feature >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > > Provide a new GSSAPI implementation using Kerby. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-551) Data type conversion between GSSAPI interface and Kerby
[ https://issues.apache.org/jira/browse/DIRKRB-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-551: --- Fix Version/s: 1.1.0 > Data type conversion between GSSAPI interface and Kerby > --- > > Key: DIRKRB-551 > URL: https://issues.apache.org/jira/browse/DIRKRB-551 > Project: Directory Kerberos > Issue Type: Sub-task >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 1.1.0 > > Attachments: DIRKRB-551-V1.patch, DIRKRB-551-V2.patch > > > Some utility functions to convert data between GSSAPI interface and Kerby -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DIRKRB-635) Backends should be optional when building kerby
[ https://issues.apache.org/jira/browse/DIRKRB-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098181#comment-16098181 ] Kai Zheng commented on DIRKRB-635: -- Thanks Colm! And thanks [~zenglinx] for the contribution. > Backends should be optional when building kerby > --- > > Key: DIRKRB-635 > URL: https://issues.apache.org/jira/browse/DIRKRB-635 > Project: Directory Kerberos > Issue Type: Improvement >Reporter: Lin Zeng >Assignee: Lin Zeng > Fix For: 1.0.1 > > Attachments: DIRKRB-635-01.patch, DIRKRB-635-02.patch > > > Now all the backends have been built when building kerby. It's too > time-consuming, and most users only need the json backend. > Besides the json backend, we should make backends optional in the building > phase. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DIRSERVER-2202) pwdHistory not getting maintained when doing modify password with ldaptive client
[
https://issues.apache.org/jira/browse/DIRSERVER-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098173#comment-16098173
]
Emmanuel Lecharny commented on DIRSERVER-2202:
--
Using the {{ModifyRequest}} to change a password won't work as you expect,
because it's not containing the {{PasswordModify}} control. This is the reason
there is a specific method in the API to do that.
Again, check the test samples that expose how to use the api in
http://svn.apache.org/viewvc/directory/apacheds/tags/2.0.0-M23/server-integ/src/test/java/org/apache/directory/server/operations/extended/PwdModifyIT.java?revision=1752913=markup
> pwdHistory not getting maintained when doing modify password with ldaptive
> client
> -
>
> Key: DIRSERVER-2202
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2202
> Project: Directory ApacheDS
> Issue Type: Bug
>Affects Versions: 2.0.0-M23
> Environment: windows, ldaptive latest, java 8
>Reporter: Hal Deadman
>
> If I connect as a non admin user and modify my own password with directory
> studio, a new pwdHistory is added.
> If I modify the password programatically, using the old/new password
> modifyPassword extended operation that should respect history, it is deleting
> all my history (and leaving a single pwdHistory entry). The code looks like
> this:
> {noformat}
> // connecting as user that is trying to change their password
> org.ldaptive.Credential cred = new
> org.ldaptive.Credential(oldPassword);
> org.ldaptive.BindConnectionInitializer bindConnectionInit = new
> org.ldaptive.BindConnectionInitializer(userDn,cred);
> org.ldaptive.ConnectionConfig connectionConfig = new
> org.ldaptive.ConnectionConfig(ldapUrl);
> connectionConfig.setUseStartTLS(false);
> connectionConfig.setConnectionInitializer(bindConnectionInit);
> DefaultConnectionFactory userLdapConnectionFactory = new
> DefaultConnectionFactory(connectionConfig);
> try (Connection conn =
> userLdapConnectionFactory.getConnection()) {
> conn.open();
> PasswordModifyOperation modify = new
> PasswordModifyOperation(conn);
> Response response = modify.execute(new
> PasswordModifyRequest(userDn, new Credential(oldPassword), new
> Credential(plaintextPassword)));
> }
> {noformat}
> Isn't the pwdHistory being maintained by the server? Why does a different
> client determine whether pwdHistory entries are added or not? (In this case
> they are not only not added but multiple entries are replaced by a single
> one).
> Ldaptive doesn't implement ldap protocol, in this case it is using JNDI as
> the provider of ldap protocol.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (DIRKRB-635) Backends should be optional when building kerby
[ https://issues.apache.org/jira/browse/DIRKRB-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved DIRKRB-635. Resolution: Fixed > Backends should be optional when building kerby > --- > > Key: DIRKRB-635 > URL: https://issues.apache.org/jira/browse/DIRKRB-635 > Project: Directory Kerberos > Issue Type: Improvement >Reporter: Lin Zeng >Assignee: Lin Zeng > Fix For: 1.0.1 > > Attachments: DIRKRB-635-01.patch, DIRKRB-635-02.patch > > > Now all the backends have been built when building kerby. It's too > time-consuming, and most users only need the json backend. > Besides the json backend, we should make backends optional in the building > phase. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DIRKRB-635) Backends should be optional when building kerby
[ https://issues.apache.org/jira/browse/DIRKRB-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated DIRKRB-635: --- Fix Version/s: 1.0.1 > Backends should be optional when building kerby > --- > > Key: DIRKRB-635 > URL: https://issues.apache.org/jira/browse/DIRKRB-635 > Project: Directory Kerberos > Issue Type: Improvement >Reporter: Lin Zeng >Assignee: Lin Zeng > Fix For: 1.0.1 > > Attachments: DIRKRB-635-01.patch, DIRKRB-635-02.patch > > > Now all the backends have been built when building kerby. It's too > time-consuming, and most users only need the json backend. > Besides the json backend, we should make backends optional in the building > phase. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DIRKRB-635) Backends should be optional when building kerby
[ https://issues.apache.org/jira/browse/DIRKRB-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098068#comment-16098068 ] Colm O hEigeartaigh commented on DIRKRB-635: OK I'll defer to you on this [~drankye]. I will merge the patch. > Backends should be optional when building kerby > --- > > Key: DIRKRB-635 > URL: https://issues.apache.org/jira/browse/DIRKRB-635 > Project: Directory Kerberos > Issue Type: Improvement >Reporter: Lin Zeng >Assignee: Lin Zeng > Fix For: 1.0.1 > > Attachments: DIRKRB-635-01.patch, DIRKRB-635-02.patch > > > Now all the backends have been built when building kerby. It's too > time-consuming, and most users only need the json backend. > Besides the json backend, we should make backends optional in the building > phase. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
